Oh, ok, well in that case I suppose the flag should cause all indexing operations to become their unsafe variants instead, all functions that call those to become unsafe, etc. propagating the unsafety where it's needed to make the code compile.
> On 28 Mar 2014, at 03:15, Daniel Micay <danielmi...@gmail.com> wrote: > >> On 27/03/14 09:02 PM, Tommi Tissari wrote: >> Compiling with that flag would figuratively speaking wrap everything inside >> an unsafe block and then omit vector bounds checking. The flag wouldn't be >> allowed for library builds. >> >> What I find a bit totalitarian about this situation is that the language >> forces a decision which the programmer should be allowed to make for >> himself. A bit like someone dictating my hair style. > > What would be the meaning in `unsafe` in that new dialect of Rust? We > already lint on redundant unsafe blocks, and *all* unsafe blocks would > be redundant in that case. It might as well just consider everything to > be inside one... > _______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
