3 ms·
Among other things, embedded support; if you want to compile out the standard library, no_std effectively requires nightly right now. Many embedded developers a
by JoshTriplett 9y ago
Among other things, embedded support; if you want to compile out the standard library, no_std effectively requires nightly right now. Many embedded developers are stuck on nightly for that reason.
I've seen some proposed solutions in progress for that, at the moment, such as standardizing panic_fmt (needed to write no_std applications).
- dbcurtis 9y agoInteresting. I haven't tried Rust yet, but it is on my "to learn what all the fuss is about" list. The main reason I'm interested is for embedded.
- JoshTriplett 9y agoIt works very well for embedded; the only problem is that to build a complete OS-style image, you tend to need nightly, either for no_std or to build your own std/core for the target platform.
- bsder 9y agoDo the Rust embedded developers all hang on an IRC room or something?
- steveklabnik 9y agoThere's #rust-osdev (which has been pretty quiet lately) and #rust-embedded at least; I think Tock has their own channel too?