Embedded is very conservative. While Rust is looking promising, it will be a while before it is trusted like the embedded subset of C++ is (that is no exceptions and other parts that embedded often turns off). That time may or not find faults with Rust (including some faults that are today considered a good thing).

The movers and shakers in the embedded C++ world are looking at Rust though.

Gonna need a citation on that one. I work in the embedded world for a billion+ dollar company and there is zero interest or adoption in Rust.

It has got enough attention that SG14 (the C++ embedded working group) is asking questions and trying to figure out what to do about it. Most of the committee seems aware of it, some have looked into it more than others.

That doesn't mean everyone is looking at it. Like I said, embedded is conservative, so it will be a while before everyone looks.

here we go:

https://blog.rust-embedded.org/newsletter-31/

autmotive (plastered with 1bn+$ companies) is actively exploring rust for functional safety, via AUTOSAR, and adacore and ferrous systems partner up for rust in ada-affine industries.

rust has this lovely habit of validating their compiler updates with their full collection of libraries, that's one step ahead of the validation contribution of SUSE, redhat, debian, canonical for common, linux packaged C/C++ libraries, because it happens on multiple OSs.

https://brson.github.io/2017/07/10/how-rust-is-tested

there is plenty of energy for formal verification of rust projects, too:

https://alastairreid.github.io/automatic-rust-verification-t...

Entire core library you mean? std is normally not supported on embedded targets AFAIK.