News for hackers. Stuff that matters.
Re:Comparing k-NN in Rust by pcwalton on Tuesday June 10, 2014 @02:13PM (#7874316)
Because usually ints are used as array indices, and you want them to be the same size as a pointer in that case.

There is an issue to remove the notion of a "default" integer type.

Re:Comparing k-NN in Rust by modeless on Tuesday June 10, 2014 @05:29PM (#7875428)
Ah, I see. Personally I think that isn't a strong enough justification, since this choice introduces possible 32/64 bit portability issues and prevents optimizations in scenarios like this. Arrays with >4 billion elements are rare and it would be a shame to compromise the language design for them.
Re:Comparing k-NN in Rust by dbaupp on Wednesday June 11, 2014 @12:18AM (#7876493)
It would also be a shame to end up with an overly restrictively language in future, where large arrays/values need special `..._64` functions (taking 64 bit integers, rather than 32 bit ones).
Re:Comparing k-NN in Rust by kazagistar on Tuesday June 10, 2014 @11:56PM (#7876443)
I like that justification, assuming there are int8, int16, int 32, int64, etc, there is no need for another int anyways.