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.
-
no-panic
Discontinued Attribute macro to require that the compiler prove a function can't ever panic
With that out of the way, this means there are a few options. One option is to simply not use any of those types. This would mean writing alternatives. Not necessarily what you'd *want*, but it is at least possible. The second would be to forbid certain APIs that may reallocate, and only allow ones that return Result. Stuff like https://github.com/rust-lang/rust/issues/48043 can be used, and other stuff could be rejected. This would require some sort of custom analysis, but is fundamentally do-able.
In my case, it is okay to panic, but https://github.com/dtolnay/no-panic does exist, even if it's not as nice as real support.
From this, it looks like they probably won't end up using liballoc directly (which is kind of what I was expecting as a very casual observer):
There is an effort to add a GCC backend to Rust, at https://github.com/antoyo/rustc_codegen_gcc .
lrs? https://github.com/lrs-lang/lib
Related posts
- Why do lifetimes need to be leaky?
- How hard would it be to port the Rust toolchain to a new non-POSIX OS written in Rust and get it to host its own development? What would that process entail?
- GCC 13 and the State of Gccrs
- Any alternate Rust compilers?
- “Rust is safe” is not some kind of absolute guarantee of code safety