Because of Rust's (relatively) bare-bones std, we have to rely on a lot of community-developed crates like chrono and serde to achieve functionalities found in other languages. This was evident while reviewing some of the CERT C -> Rust categorization batches, which is why it was considered appropriate to discuss what could be done from our part to bridge the gap between users wanting to adopt Rust for their safety-critical projects and the heavy use of non-std crates.
One idea that came up is that this could also be a potential joint-effort between the Safety-Critical Rust Consortium and the Secure Code working group as it could be of mutual interest given the nature of this proposal.
Because of Rust's (relatively) bare-bones
std, we have to rely on a lot of community-developed crates likechronoandserdeto achieve functionalities found in other languages. This was evident while reviewing some of the CERT C -> Rust categorization batches, which is why it was considered appropriate to discuss what could be done from our part to bridge the gap between users wanting to adopt Rust for their safety-critical projects and the heavy use of non-stdcrates.One idea that came up is that this could also be a potential joint-effort between the Safety-Critical Rust Consortium and the Secure Code working group as it could be of mutual interest given the nature of this proposal.