Re:Rust Sucks If I Fail to Write X
by burntsushi on Friday February 17, 2017 @06:10PM
(#13672519)
Yes, it can be tricky. One of the problems is that we don't have the memory model completely worked out.
I don't know how much harder it is than C/C++ though. Seems hard to quantify. But the `unsafe` markers should help quite a bit.
There are a bunch of things that are UB in C and C++ that are well-defined in Rust.
* Signed integer overflow * Aliased pointers to different types (-fno-strict-alias) * Probably more, but the formalised memory model is still up in the air. The ones I just listed are just the ones that are already decided...
True, in fact undefined-behaviour-wise I don't think there is any mainstream
language that comes close in this respect to C/C++. Alas, this is well-known
and addressed in various publications.
Converse, things that could be eventually decided to be UB in Rust, but are not UB in C/C++, is rarely mentioned at all. It is quite interesting what is cost (in terms of UB behaviour) of making various optimization that are claimed to be possible in Rust but not yet realized. Reading through some of Niko proposals it would seems that this cost is quite nontrivial.
Writing unsafe code in Rust is harder than doing it in C/C++, because Rust introduces a whole new class of undefined behaviours that is just absent from C/C++. See [0], [1] or [2] in general for examples.
[0] http://smallcultfollowing.com/babysteps/blog/2017/02/01/unsa...
[1] http://smallcultfollowing.com/babysteps/blog/2016/05/27/the-...
[2] https://github.com/nikomatsakis/rust-memory-model