getrandom
dislike-in-rust
Our great sponsors
getrandom | dislike-in-rust | |
---|---|---|
8 | 2 | |
254 | 11 | |
2.0% | - | |
7.0 | 0.6 | |
12 days ago | about 1 year ago | |
Rust | ||
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.
getrandom
-
We have getrandom at home
The crypto source in Go is great, no complaints there. Lints like gosec even recommend using it when generating crypto entropy. Go did a good job here, and I expect Rust will do the same sometime after getrandom reaches 1.0 so the API questions are settled, plus whatever makes sense for the future-proofing the standard library needs.
-
Fellow Rust enthusiasts: What "sucks" about Rust?
I would wait for the getrandom crate to reach 1.0, which will answer many of the questions around what an API like this can look like, and then maybe the standard library discussion will be on firmer footing because at least we'll know what API we want to immortalize. Rushing that now just to save people importing a small crate does not seem to be the way to go.
-
Introduction to Random Number Generation in Rust
I'd caution against using /dev/random directly, and instead recommend using getrandom. It's effectively the same thing on Haiku and Redox, but is cross-platform and will upgrade to better sources on various platforms as available (such as using the getrandom() call on Linux and Android, or getentropy() on macOs, if avaialable).
-
Alea: fast and easy random number generation in Rust
getrandom
-
Why I rewrote my Rust keyboard firmware in Zig: consistency, mastery, and fun
It's a default, but overwritable behavior, see the #[path] attribute. You still have to create N files for each supported platform, but at the top level you will see only one module. On of the crates which uses this approach in practice is getrandom.
-
String, Vec<T>, Box<T>, Rc<T>... could be moved from alloc to core
IIUC the main problem which prevents from moving HashMap & co to alloc is lack of API to get system entropy which is required for DOS protection. Ideally we would have a #[global_allocator]-like functionality for retrieving system entropy. Relevant issue: https://github.com/rust-random/getrandom/issues/21
dislike-in-rust
-
Fellow Rust enthusiasts: What "sucks" about Rust?
I'm so glad you asked: https://github.com/Lucretiel/dislike-in-rust
-
[Blog post] When Rust hurts
I've been unapologetic about my adoration for rust (even some of the weirder stuff (eg * vs ref), which still somehow plays directly into my intuitions and comfort zone when programming). I know there's stuff I don't care for, but when put on the spot I can never recall what any of it is, so I started a public list of all the things I'm not a fan of, just so that I don't come off as a total shill.
What are some alternatives?
nanorand-rs - A tiny, fast, zero-dep library for random number generation
rust-delegate - Rust method delegation with less boilerplate
pollster - A minimal async executor that lets you block on a future
storages-api
gosec - Go security checker
rust-orphan-rules - An unofficial, experimental place for documenting and gathering feedback on the design problems around Rust's orphan rules
rand - A Rust library for random number generation.
SHLL - An experiment of high level code optimization
azure-sdk-for-net - This repository is for active development of the Azure SDK for .NET. For consumers of the SDK we recommend visiting our public developer docs at https://learn.microsoft.com/dotnet/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-net.