by steveklabnik on 10/3/2024, 4:34:10 AM
by spease on 10/3/2024, 7:13:18 AM
No. This is lazy, and ignores how Rust is unique.
What would be better is to have a set of standard traits that libraries can implement to provide a service.
Effectively, create a standard and let other people build things that adhere to that standard.
This gives the freedom to people to choose what implementation best suits their purpose, but still be able to write code that’s decoupled from a specific library in case it disappears.
Another standard library would just be like boost in C++. That sort of makes sense if you have no package manager so integrating new libraries is a nightmare, and type-safety is pretty lax, but Rust is on the opposite side of both of those things.
by cloudhead on 10/3/2024, 7:46:01 AM
Even better would be to have some of the basics in the standard library, like Go and Zig.
by p0w3n3d on 10/3/2024, 4:58:43 AM
Time! You forgot about time API. The hardest thing in the world, to setup meeting with a person in Asia on the day before they switch to a DST
by daghamm on 10/3/2024, 8:35:19 AM
How can Rust claim to be secure if you can't do even the smallest task without importing a bunch of random crates?
This has been suggested and tried over the years, even with the same name: https://crates.io/crates/stdx
In practice, they don’t gain adoption. The current situation is just better, or at least, many more people seem to think that in practice.