4 ms·
Definitely. We’re currently blocked with the builtin await using thread local storage, but that’s planned to be removed and replaced with something that will wo
by Nemo157 8y ago
Definitely. We’re currently blocked with the builtin await using thread local storage, but that’s planned to be removed and replaced with something that will work without an OS before stabilisation.
I have had the old macro based async code in Rust running on a Cortex M device, completely runtime free. Once the TLS stuff is sorted I plan to port this forward to work with the builtin syntax.
- bluejekyll 8y agoWhat’s the TLS stuff to be sorted out?
- steveklabnik 8y agoIIRC, the initial implementation of async/await requires TLS. Eventually it won’t.
- bluejekyll 8y agoOh! For some reason I jumped to Transport Layer Security, not Thread Local Storage... duh. Yeah the Pinning stuff is supposed to help with this as I understand.
- steveklabnik 8y agoAh! Super reasonable, yeah. It can be confusing.
- jononor 8y agoSuper excited about that! This will be a major feature for embedded devices which perform network I/O, be it Internet of Things or industrial control over Ethernet.
- eddyb 8y agoI don't understand why people don't just support TLS in non-userspace code. It's so convenient for a bunch of things, and sadly Rust, for now, has nothing in between "fully explicit argument passing" and "scoped global state".