News for hackers. Stuff that matters.
Re:The Performance Cost of Integer Overflow Checking by SamReidHughes on Thursday December 18, 2014 @02:19AM (#8766345)
Other ways in which the choice of what constitutes safety is convenient: you can recurse until the stack overflows, and you can make infinite loops instead of having to prove through the type system that everything terminates. These are reasonable design decisions. If allowing silent integer overflow is the wrong choice for Rust, it's barely the wrong choice, because the costs and benefits are clearly arguable and user-specific.
Re:The Performance Cost of Integer Overflow Checking by leoc on Thursday December 18, 2014 @11:10AM (#8767914)
> These are reasonable design decisions. If allowing silent integer overflow is the wrong choice for Rust, it's barely the wrong choice, because the costs and benefits are clearly arguable and user-specific.

Seems reasonable to me, and I certainly didn't demand overflow-checking by default in Rust. (OTOH, twelve hours ago you were so disappointed with that decision that it undermined your confidence in the Rust team...) But I don't see what that has to with picking the definitions for desirable adjectives like 'safety' when it comes to promoting or describing a system.

Re:The Performance Cost of Integer Overflow Checking by SamReidHughes on Thursday December 18, 2014 @01:35PM (#8768849)
> OTOH, twelve hours ago you were so disappointed with that decision that it undermined your confidence in the Rust team...

Well it's relatively small damage levels but it's the wrong decision, and it's the inoffensive choice made of status quo bias.