Re:Ask HN: Will Rust replace C/C++? What's holding it back? ...
by now on Thursday November 22, 2018 @11:46AM
(#18511015)
gets
Re:Ask HN: Will Rust replace C/C++? What's holding it back? ...
by steveklabnik on Thursday November 22, 2018 @03:57PM
(#18512499)
I’m not sure what you’re saying exactly. You’re referring to the inherently dangerous c function?
> I mean, if something isn't specified in the docs and the compiler changes its behaviour in this area, is it a bug?
Since Rust is so strongly typed, we do have strong rules for many kinds of changes, even if there's no formal specification. That can only help with some things, but it does help a lot.
> it changes pretty fast
The key here is that the changes are additive, that is, we don't make egregious backwards incompatible changes. We do sometimes for things like soundness fixes, but even then, we have tooling to estimate the impact of breakage on the ecosystem, and have strategies for easing that pain. Most users report that their code never breaks, and virtually all of the users whose code has broken report that it was trivial to get building again.