rand
rayon
Our great sponsors
rand | rayon | |
---|---|---|
29 | 66 | |
1,553 | 10,082 | |
2.4% | 2.9% | |
8.2 | 9.0 | |
6 days ago | 2 days ago | |
Rust | Rust | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rand
-
We have getrandom at home
Making compatibility promises for distributions means they cannot take advantage of potential advancements in the field.
-
Blog Post: On Random Numbers
Defining an error type that is meaningful, portable, and compatible with no-std isn't straightforward. If the std lib's getrandom requires std, then just like that, rand and many other crates won't use it anyway. Using io::Result seems to me to face this challenge.
-
Hey Rustaceans! Got a question? Ask here (52/2022)!
Some wasm targets can’t generate random numbers at all but in the case of the book because you are using wasm in a browser you can use JS to generate random numbers. I believe there’s a way to get the rand crate to use JS as the backend for generating rand but its a bit more convoluted than the easy one-liner that the book suggests.
- Data-driven performance optimization with Rust and Miri
-
What crates are considered as de-facto standard?
rand
- Why Rust?
-
[Media] Nebulabrot rendered with Rust — Explanations in the comments
This uses rand and xcomplex to handle the mathematics, png to write image files, and dialoguer and indicatif for some pretty prompts and progress bars.
-
Do you ever use unsafe { .. } when not implementing custom data structures or interacting with external C code?
You can often achieve this without any unsafe by putting an assert!() on the length before the hot loop. For example, I got rid of some unsafe in rand that way.
-
Original source of `(seed * 9301 and 49297) % 233280` random algorithm?
This is a widely used method to map random integers to floating point numbers, but it has the disadvantage of wasting 1 bit of float mantissa precision.
On modern CPUs, its computational advantage over full-precision mapping methods, such as multiplication by a float, is not always clear [1].
-
Any plans for built-in support of Vec2/Vec3/Vec4 in Rust?
In fact, there are a lot of crates in Rust where in other programming languages, it would be included in the standard library. Examples are regex, random number generators, additional iterator methods, macros for other collections, num traits, loggers, HTTP libraries, error handling, async runtimes, serialization and deserialization, date and time, and many more.
rayon
- Too Dangerous for C++
-
What Are The Rust Crates You Use In Almost Every Project That They Are Practically An Extension of The Standard Library?
rayon: Async CPU runtime for parallelism.
-
Moving from Typescript and Langchain to Rust and Loops
In the quest for more efficient solutions, the ONNX runtime emerged as a beacon of performance. The decision to transition from Typescript to Rust was an unconventional yet pivotal one. Driven by Rust's robust parallel processing capabilities using Rayon and seamless integration with ONNX through the ort crate, Repo-Query unlocked a realm of unparalleled efficiency. The result? A transformation from sluggish processing to, I have to say it, blazing-fast performance.
-
The Rust I Wanted Had No Future
(see https://github.com/rayon-rs/rayon/tree/master/src/iter/plumbing)
-
General Recommendations: Should I Use Tree-sitter as the AST for the LSP I am developing?
Sequentially, generating tree-sitter AST for each file and querying for the links of each file takes around 2.3 seconds. However, I randomly remembered this crate rayon, and I decided to test it. It ended up improving the performance (just by changing 2 lines of code) to 200-300ms by parallelizing the iterators and tree-sitter queries. MAJOR.
-
python to rust migration
Now if you really want to use Rust, you can rewrite only the part that are slowing down your consumer. It's easy by using Py03 and maturin. Maybe also rayon to parallelize.
-
AI learns to play flappy bird (code in comments)
Maybe rayon could make some loops there and there faster if needed.
-
Making Python 100x faster with less than 100 lines of Rust
One of the others understated pros of rewriting some parts in Rust, it's that you can parallelize easily with Rayon[0]
-
Trying to learn by tutorials, for cannot find a single Actix/Diesel tutorial that actually compiles
On that topic, have you heard about our lord and savior rayon? 😊
-
Brett Slatkin: Why am I building a new functional programming language?
> He spoke of the potential for functional languages to provide a significant, intrinsic advantage when it comes to parallel computing.
> (...)
> If that were true, you'd expect that the many existing functional programming languages would have already satisfied this need. But in my opinion, they haven't
Well there is https://futhark-lang.org/ - it runs on the GPU, and is awesome.
On the CPU side, I think that Rust plus https://github.com/rayon-rs/rayon was a huge breakthrough on writing parallel programs using both functional and imperative programming, and future languages should learn from its successes. The ownership system & the borrow checker, plus other type-level features like the Send and Sync traits, were essential to enable sharing read-only data between threads without synchronization, or sharing read-write data with synchronization, all checked at compile time for data races (which is a huge problem to solve, and is something that neither Go nor Java protects against at compile time)
Indeed Futhark shares a key feature with Rust: it uses uniqueness types to enable in-place updates, which is kind like a limited form of Rust ownership: if you are the sole user of some memory, you can update it and other code will be none the wiser. This kind of thing is very important to build functional programs that are performant in practice.
What are some alternatives?
crossbeam - Tools for concurrent programming in Rust
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
RxRust - The Reactive Extensions for the Rust Programming Language
rust-numpy - PyO3-based Rust bindings of the NumPy C-API
tokio-rayon - Mix async code with CPU-heavy thread pools using Tokio + Rayon
sqlx - 🧰 The Rust SQL Toolkit. An async, pure Rust SQL crate featuring compile-time checked queries without a DSL. Supports PostgreSQL, MySQL, and SQLite.
coroutine-rs - Coroutine Library in Rust
libfringe - a Rust library implementing safe, lightweight context switches, without relying on kernel services
rxRust - Rust implementation of Reactive Extensions.
rust-postgres - Native PostgreSQL driver for the Rust programming language
fastrand - A simple and fast random number generator
PyO3 - Rust bindings for the Python interpreter