stdx VS safety-dance

There's none that I know of, aside from stdx which was last updated 4 years ago.

⭐ stdx - The missing batteries of Rust - Brian Anderson

brson had a repository called https://github.com/brson/stdx and it's a pity it isn't maintained anymore: some of them are in disuse now (for example, instead of lazy_static prefer stdlib's Lazy, or better yet, you don't need them if you just want to initialize a mutex or something; also error-chain) and the list could use some maintenance

You suggested creating a super-library of vetted crates. It has been tried before, but it didn’t get any adoption. stdx - The missing batteries of Rust was never used much. Looking at it now, it recommends crates that have been superseded by others.

As an example of the above, if you're not aware of it already, you might find brson/stdx interesting.

Big libraries like Boost or the Python standard library tend to develop as a workaround for weak package management so, with Cargo, efforts to produce Boost-like compilations (Eg. stdx) withered on the vine for lack of sufficient interest.

It's been suggested and people even tried doing that of their own volition with projects like stdx, but they withered away for lack of interest.

I second u/globulemix' attitude, searching on crates.io and then looking at Downloads and also git activity (might be misleading, as some projects are simply very stable). For a lot of tasks, you might wish to take a look at stdx

Seems abandoned, but there was https://github.com/brson/stdx

I've been here since before Rust 1.0 and I've seen various projects like stdx start, but fail to achieve critical mass... probably because that kind of approach tends to invite the worst kind of bikeshedding.

[2]: https://github.com/rust-secure-code/safety-dance

The most "virtuous"/desirable statement in this topic is probably the "100% safe code now - while being faster than the C version!" on the rust-secure-code/safety-dance entry for miniz_oxide.

According to the rust-secure-code/safety-dance trophy case, their audit left miniz_oxide 100% safe and faster than the C version.

Efforts that don't try to pick winners, but just to help packages that already exist, like Rust Safety Dance and developing tools like Miri. (And that dependency-improving sprint, the name of which eludes me, but which was mentioned in TWIR a while ago.)

I'm similarly iffy on using a parser for something as web-exposed as e-mail which uses unsafe for a performance boost without a thumbs-up from someone like /u/Shnatsel and the Safety Dance.

Since this all happened, the safety-dance project has come into existence, which aims to channel the mob into doing useful things, not just piling onto someone who's got different views on what they want from Rust.

https://github.com/rust-secure-code/safety-dance is always looking for contributors.