Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
zig
General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
-
Joda-Time
Joda-Time is the widely used replacement for the Java date and time classes prior to Java SE 8.
-
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.
Wasmer attempted to do this in the Ziglang repo barely 4 days ago:
https://github.com/ziglang/zig/issues/17115
>> Note that boost is also not the C++ standard library.
I know, but many components that are now in the C++ standard library were previously in Boost or were heavily influenced by / inspired by Boost:
https://stackoverflow.com/questions/59912393/boost-libraries...
Similar events also happened in Java 8 with the Joda time library:
https://www.joda.org/joda-time/
>> serde's main maintainer is also a member of the libs team, so it being moved into the standard library meaning more maintenance doesn't really make sense to me.
I did not know that.
I was just using serde as an example of a widely-used crate that feels essential enough to be included in the Rust standard library.
At what point does a third-party crate become so useful that it might be considered for inclusion in the Rust standard library?
Is there a process for adding crates to the Rust standard library?
If so, how do such crates get nominated and approved?
https://github.com/dancrossnyc/rxv64
And go for practically anything outside that scope: web service, CLI tool, etc.