Woah, hey there. Here's a project that needs help. It's called stdx and it wants to collect all those libraries that everybody uses that aren't std into one place. You can think of it as both a guide to the crate ecosystem for newbies as well as an extendend, 'batteries-included' standard library. I…

I really don't think either crate should be exposed by stdx. libc is a very popular create because it is a dependency of many other libraries; both libraries are really second order-libraries (libraries for libraries).

@stebalien I'd argue that std is exactly a "library for a library", so putting it in stdx doesn't seem that crazy. Although it's perhaps a bit "rude" for a simple library to depend on stdx, it's a great way to get started (and "free" if your consumer depends on it too!).

Half joking: if stdx 0.102 is for Rust 1.2.0, this scheme will overflow in "only" 11 years when Rust 1.100.0 is released. (And as mentioned elsewhere, not releasing Rust 2.0 for a long time would be a sign of success IMO.)

I think it is redundant with crates.io . I'd really prefer an update of crates.io to mention (with keywords/categories etc ...) that these libraries are for generating random numbers and this one in particular is considered the best in most situations. The workload looks similar but it avoids havin…

[image] retep998: I think it's kinda silly that libc is included, which is a disorganized mess of ffi bindings, but not winapi. The current list is just what I picked to bootstrap the idea. We can add more!

[image] SimonSapin: Half joking: if stdx 0.102 is for Rust 1.2.0, this scheme will overflow in "only" 11 years when Rust 1.100.0 is released. What an amazing problem to have! When the time comes I will remember to point to your post and say 'you called it'. Seriously, though we can still chan…

[image] tafia: I think it is redundant with crates.io.I'd really prefer an update of crates.io to mention (with keywords/categories etc ...) that these libraries are for generating random numbers and this one in particular is considered the best in most situations.The workload looks similar but …

I've filled out descriptions of the existing crates . Things I'd like to do next: Add more crates based on the suggestions here Add a usage faq. A guide with simple recipes for common tasks, hopefully that combine the libraries in interesting ways. Doubles as a test suite (*). Get reexported macros…

+1 for one crate per thing. Do one thing, do it best is the right way. If you look at the Clojure ecosystem, they used to have such a stdx thing called clojure.contrib. But it was soon broken into several minimal libraries focus on only one purpose, like data.csv, data.json, core.match, core.cache.…

Stdx - The missing batteries of Rust

brson August 5, 2015, 12:35am 51

I'm not going to be able to get a release out for Rust 1.2, but I am still keen on curated libs and want to get back to this in time to release for 1.3.

Topic		Replies	Views
Rust should have a big standard library and here's why community	101	18120	March 6, 2020
Standard library vs crates	32	3746	November 14, 2021
Stdx updated for Rust 1.19	7	1738	July 19, 2017
Why are there no concurrent collections in std? help	31	13309	April 27, 2019
Feedback on Rust Programming Language / std	23	1274	September 3, 2025

Stdx - The missing batteries of Rust

Related topics