News for hackers. Stuff that matters.
Re:A half-hour to learn Rust by GordonS on Saturday February 29, 2020 @08:00AM (#22450324)
Meh, 123_i32 seems like a big improvement to me, but with the others, I just can't immediately grok it - it's having numeric digits as part of the type name that throws me.

I realise of course that not everyone will feel the same.

Re:A half-hour to learn Rust by cyphar on Saturday February 29, 2020 @09:57AM (#22450848)
C99 has effectively identical types in the standard library (uint8_t ... uint64_t, and ditto for int8_t ... uint64_t). There are very few modern C codebases where I haven't seen these used (personally I use them because it's much easier than remembering what is the minimum guaranteed size of unsigned long). The Rust ones have just slightly more terse names (which it's understandable to dislike, though I personally find the endless _t suffixes in C type names to be a bit annoying as well). And Rust's usize is basically uintptr_t.
Re:A half-hour to learn Rust by GordonS on Saturday February 29, 2020 @06:11PM (#22453883)
Sorry, I should have phrased that better; it's more like, having numeric digits as part of the type name that immediately follows the value throws me.

So something like this (rust):

`16i32`

Compared to something like this (C#):

`16i`