Our great sponsors
-
sccache
Sccache is a ccache-like tool. It is used as a compiler wrapper and avoids compilation when possible. Sccache has the capability to utilize caching in remote storage environments, including various cloud storage options, or alternatively, in local storage.
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
Use sccache to cache local compilations. I've done this in the past, but it has been too fragile and I finally gave up. In any case, I still had to recompile on every Rust release, and every release of a given crate — in parallel with people all over the world.
The difference compared to "stdx" is the binary distribution. I think it would be easier to have one library doing it rather them all crates on crates.io and we also get the feeling of having something semi-official, rather them just lots of smaller crates.
You neglected to mention that there was a lazy_static to Serde's once_cell: rustc_serialize. In fact, I could be wrong, given how long it's been (I didn't really move from watching to writing my own code until the v1.0 stability promise), but I think it might have been part of the standard library before v1.0.
What’s more likely is crates like syn, serde and others being distributed in binary via crates.io, possibly in wasm (https://github.com/dtolnay/watt). These don’t end up in the final binary anyway, they only generate code via macros. It would be a big win for compile times.
It's not officially deprecated, but the alternatives on crates.io are considered better. flume and crossbeam-channel feature less unsafe code and offer better performance. Benchmarks.
Adding to the other comment, it also has longstanding issues that are hard to fix https://github.com/rust-lang/rust/issues/39364