Skip to content

Commit 6334c48

Browse files
authored
Merge pull request #115 from jturner314/update-ndarray
Update to ndarray 0.12.0
2 parents 4f273ac + 1574286 commit 6334c48

File tree

2 files changed

+7
-8
lines changed

2 files changed

+7
-8
lines changed

Cargo.toml

+1-2
Original file line numberDiff line numberDiff line change
@@ -30,8 +30,7 @@ version = "0.2"
3030
default-features = false
3131

3232
[dependencies.ndarray]
33-
version = "0.11.2"
34-
git = "https://github.com/bluss/ndarray"
33+
version = "0.12"
3534
features = ["blas"]
3635
default-features = false
3736

README.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -24,8 +24,8 @@ There are two ways to link LAPACKE backend:
2424
There are three features corresponding to the backend implementations (`openblas` / `netlib` / `intel-mkl`):
2525

2626
```toml
27-
[depencdencies]
28-
ndarray = "0.11"
27+
[dependencies]
28+
ndarray = "0.12"
2929
ndarray-linalg = { version = "0.9", features = ["openblas"] }
3030
```
3131

@@ -34,8 +34,8 @@ For the sake of linking flexibility, you can provide LAPACKE implementation (as
3434
You should link a LAPACKE implementation to a final crate (like binary executable or dylib) only, not to a Rust library.
3535

3636
```toml
37-
[depencdencies]
38-
ndarray = "0.11"
37+
[dependencies]
38+
ndarray = "0.12"
3939
ndarray-linalg = "0.9"
4040
openblas-src = "0.5" # or another backend of your choice
4141

@@ -53,8 +53,8 @@ extern crate openblas_src; // or another backend of your choice
5353
If you creating a library depending on this crate, we encourage you not to link any backend for flexibility:
5454

5555
```toml
56-
[depencdencies]
57-
ndarray = "0.11"
56+
[dependencies]
57+
ndarray = "0.12"
5858
ndarray-linalg = { version = "0.9", default-features = false }
5959
```
6060

0 commit comments

Comments
 (0)