News for hackers. Stuff that matters.
Re:Smoltcp: A small TCP/IP stack in Rust by steveklabnik on Friday June 21, 2019 @09:22AM (#20242262)
Because the root cause is smaller than “anything anywhere”, and you can control that scope. Rust gives you tools to deal with this. It is true that if you don’t use those tools, they can’t help you.

You can’t make a convention in C++ in the same way, because the safety aspect is not part of the language. I mean, you can, but it won’t help you the same way Rust will.

Re:Smoltcp: A small TCP/IP stack in Rust by foldr on Friday June 21, 2019 @10:38AM (#20242849)
A more reasonable statement would be something like "Rust makes it easier than C++ to write modules that wrap unsafe operations behind safe interfaces". That's true, but it's not true that module boundaries somehow inherently contain the effects of unsafe code. It's pretty clear that they can't do this, given that the code all ends up being linked into one executable. Thus, makomk's original comment seems entirely correct to me.