Rust After the Honeymoon

Re:Rust After the Honeymoon by nindalf on Monday October 12, 2020 @05:31AM (#24752758)

> If you are using no_std isn't that the same as just not having a C standard library

No. no_std means that all standard library functions that involve allocation aren't available. Things like std::collections::{Vec, HashMap} etc. You have access to std::core (https://doc.rust-lang.org/core/index.html), which is pretty useful.

[ Parent | on HN ]

Re:Rust After the Honeymoon by chrismorgan on Monday October 12, 2020 @05:47AM (#24752845)

Technical correction: core is a crate, not a module in the std crate. Your paths will be core::, not std::core::.

[ Parent | on HN ]

Re:Rust After the Honeymoon by saurik on Monday October 12, 2020 @10:44AM (#24754819)

The context was with respect to memory overhead, so can you explain this difference with respect to that axis, showing that C with no standard library somehow has higher memory overhead than Rust with no_std? With respect to the actual conversational context, I stand by my comparison.

[ Parent | on HN ]

Re:Rust After the Honeymoon by strbean on Monday October 12, 2020 @06:43PM (#24760329)

I think the point is that running no stdlib in C is throwing the baby out with the bathwater.

[ Parent | on HN ]