News for hackers. Stuff that matters.
Re:Why Go Is Not Good (2014) by jerf on Wednesday December 09, 2015 @12:31PM (#10705141)
"Not quite true, the language could implement checked over- or under-flows (I believe Swift does)"

I am one of the apparently about ten people who thinks that should be the universal default. The vast bulk of people disagree, and I was trying not to poke the sleeping dog. :)

Re:Why Go Is Not Good (2014) by masklinn on Wednesday December 09, 2015 @01:07PM (#10705483)
> I am one of the apparently about ten people who thinks that should be the universal default.

There's a handful of us, a handful!

FWIW Rust checks for overflow in debug mode, and while that's elided by default when compiling with optimisations it can be re-enabled with a -Z flag:

    > rustc test.rs
    > ./test
    thread '<main>' panicked at 'arithmetic operation overflowed', test.rs:4
    > rustc -O test.rs
    > ./test
    Overflowed!
    > rustc -O -Z force-overflow-checks=on test.rs
    > ./test
    thread '<main>' panicked at 'arithmetic operation overflowed', test.rs:4
And of course some languages bypass the whole thing by automatically promoting to dynamically sized integrals.
Re:Why Go Is Not Good (2014) by jerf on Wednesday December 09, 2015 @03:41PM (#10706574)
Well, that's that then; now I just need a Rust project and I'll start learning it. (I'm only an early adopter of languages, not a bleeding-edge adopter.)
Re:Why Go Is Not Good (2014) by Gankro on Wednesday December 09, 2015 @02:54PM (#10706249)
"everything is floats" is also technically a solution, but with a curious fail-state.