faer-rs VS crates.io

On the contrary, it seemingly can be used to make a BLAS implementation (example in a PR: https://github.com/sarah-ek/faer-rs/pull/37)

see the official website and the docs.rs documentation for code examples and usage instructions.

`faer` is a collection of crates that implement linear algebra routines in pure Rust. the aim is to eventually provide a fully featured library for linear algebra with focus on portability, correctness, and performance.

see the [official website](https://faer-rs.github.io) and the docs.rs documentation for code examples and usage instructions.

---

this release implements the initial design of the high level api (see https://docs.rs/faer/0.11.0/faer/), which should allow users to get started with writing easy to read code without having to deal with managing memory or multithreading settings on their own.

i also added a thin compatibility layer with ndarray and nalgebra. this way users are able to mix and match libraries if they wish to do so, or to help with migration to different libraries

Faer is comparable to Eigen in most of their benchmarks, so they are getting closer.

performance compared to openblas is shown in the benchmarks on the repository, and on the website. (ndarray is using openblas)

currently working on a very efficient linear algebra library https://github.com/sarah-ek/faer-rs

Rust has a rich ecosystem of frameworks and libraries that let you read, parse, and manipulate text files, interact with cloud services and databases, and perform any other job that your project's development workflow may require. And because of its strong typing and tight memory management, you are much less likely to write programs that behave unexpectedly in production.

All the code discussed in this article can be accessed through this repository. For integration with existing projects consider using keyword_extraction crate available on crates.io.

So, be sure to double-check your critical libraries and be sure their alternatives exist in the Rust ecosystem. There’s a good chance the crates you need are available in Rust's crates.io repository.

The previous section was very simple, this section is also very simple but introduces us to cargo which is Rust's package manager, as a JS dev my mind goes straight to NPM.

Now, there has to be a place where all these packages come from. Similar to npmjs registry, where all node packages are registered, stored and retrieved, Rust also has something called crates.io where many helpful packages and dependencies are registered.

Before proceeding, let's check https://crates.io/, the official Rust package registry.

The most thrilling aspect has been the joy of writing the backend. It's like every struct, enum, and method in Rust forms this interconnected Multiverse of code , which you can see in crates.io which is best Documentation experience I Ever Had.

5. Crates.io

When using crates from eg. crates.io, and also things like std and core

Vendoring your packages was very tedious to even remotely get to work with Cargo. I spent a very long time getting Cargo to work together with cargo-local-registry. We vendor crates from crates.io and a custom internal registry.