On 27/03/14 07:16 PM, Lee Braiden wrote: > I think the point is that the compiler should not be forcing people to > do things, but enabling people to do things, with sensible defaults. > > Personally, whilst I would advocate MORE bounds checking in rust for > debugging / prototyping purposes, I don't think bounds checking is even > ideal. It's a useful tool WHILST prototyping software, but if you > really want to ensure quality, you do a full QA process, examining all > boundary and corner cases closely. When that's been done, then bounds > checks become both unnecessary, and inefficient. No, not massively > unnecessary or inefficient, but unnecessary and inefficient, all the same.
You're free to opt-in to non-checked indexing on a case-by-case basis where you are reasonably sure it is correct. Rust already has the necessary unsafe indexing support in the standard library.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
