3 ms·
Don't forget, "losing the standard library" doesn't mean losing everything; it means losing libstd, but not libcore. A lot of those headers you're showing off w
by steveklabnik 10y ago
Don't forget, "losing the standard library" doesn't mean losing everything; it means losing libstd, but not libcore. A lot of those headers you're showing off would be in libcore, not in libstd, in Rust terms.
> C and its current compilers are light years ahead of rustc in terms of optimisation,
Given that we use LLVM, which is the part of clang that does most of the optimizing, we should be equivalent here, roughly.
(That said, I agree that there's more we can do to make this easy.)
- shakna 10y agoI really don't like that I lose anything, but sure. Rust isn't yet equivalent to clang in terms of LLVM, because of the overhead of some of the libraries that it needs. Like its own malloc implementation. These are acceptable costs to get security. I hope I haven't come across as disliking Rust, because I love it. Unfortunately, when it comes to embedded, bytes matter, and those overheads aren't easy to limit or abolish in a simple manner. So you lose out on the security, and have strange compression scripts, or you lose out on the security and use C. For now, the second is an easier sell to a manager. I am expecting there will be progress here, from a few of the issues I've seen open on GitHub. And I really like your work.
- pcwalton 10y agoRust doesn't need its own malloc implementation.