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.
-
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.
I'm pretty certain this isn't actually true. You should look at the editions, etc. Rust also has an insane guarantee which I am certain C/C++ don't offer: It rebuilds its entire library ecosystem each time it ships to make sure nothing breaks (https://crater.rust-lang.org). I've never seen an instance were old code didn't compile on a new compiler. Rust isn't forwards compatible (new code compiles on an old compiler) of course, but what is?
Rust has an official foundation, a development governance model based on community RFCs and formal teams in charge of the language, the compiler, the standard libraries, etc. It has formal backwards compatibility guarantees, including the ability to target the compiler at a particular "edition" of the language. ABI stability is not a goal of Rust, but the Linux kernel does not have internal ABI stability either (a constant source of problems for closed source drives). C ABI compatibility is available for functions/structs/etc. on an opt-in basis.
GCC-rs isn't intended for bootstrapping, it is intended to be an actual fully featured Rust compiler in the future, mrustc is a Rust compiler intended for bootstrapping though. GCC-rs is still very early targeting an older version of the reference compiler without things like a borrow checker, but that's not going to be the case forever. The GCC-rs folks have expressed interest in re-using the borrow checker library used by the reference compiler called polonius enabling them to relatively easily add borrow checking.
Here's the tracking issue for unstable features used.
You would do the community a favor by not replying reactively. Try instead to educate yourself by reading what it took to bring https://github.com/psurply/dwfv project compilation from 2 minutes down to 20 seconds: https://blog.kodewerx.org/2020/06/the-rust-compiler-isnt-slow-we-are.html
Linus also made those C++ comments long before he did his "soul searching" to learn how to be empathetic. I mean, this exists: https://github.com/torvalds/subsurface-for-dirk
There also is the formal in progress specification: https://github.com/ferrocene/specification