News for hackers. Stuff that matters.
Re:The Performance Cost of Integer Overflow Checking by lifthrasiir on Thursday December 18, 2014 @12:48AM (#8766154)
Asides from pcwalton's argument, I think any successful (or to-be-successful) language is trying to solve some problems very well and other problems reasonably well. For Rust, the former includes the memory safety and the latter includes the integer overflow detection (but you can always name a lot more). It would be very hard to solve all problems at once (especially when known solutions to some problems worsen other problems, as seen in Rust). That can be said to Swift as well, it just picked different problems to solve very well.
Re:The Performance Cost of Integer Overflow Checking by SamReidHughes on Thursday December 18, 2014 @02:46AM (#8766384)
I don't think it's hard to solve the problem of memory safety and integer overflow detection at the same time.
Re:The Performance Cost of Integer Overflow Checking by lifthrasiir on Thursday December 18, 2014 @03:24AM (#8766447)
Both problems are undergoing active research. They are indeed orthogonal (albeit one can somehow reduce the severity of another and vice versa), but with a finite resource and time you sometimes have to choose.