(no title)
hungnv | 5 years ago
Why its not int64, int32, unsigned_int32, vec, function for all language, but inventors have to change these to u64, i64, fn...etc?
hungnv | 5 years ago
Why its not int64, int32, unsigned_int32, vec, function for all language, but inventors have to change these to u64, i64, fn...etc?
hansvm|5 years ago
Languages have many competing goals. It shouldn't take long to get used to u64 over, e.g., unsigned_int64, and brevity is valuable in its own right. Too many wasted characters can obscure the flow of a program and make it slower to read and understand.
Is it the right choice? I could be persuaded either way. I know it's one I've personally made before, choosing rebindings like i256 and cmpeq8 when doing a lot of bit-twiddly vector code.
tkzed49|5 years ago
BiosElement|5 years ago
Having said that, less typing and clutter are also beneficial, so it's really a net natural debate.
viraptor|5 years ago
Santosh83|5 years ago
pfalcon|5 years ago
Jumping thru hoops is what Zig seems to choose with its unorthodox, different-just-to-be-different syntax. I wonder, how many will want to jump with it?
didibus|5 years ago
pjmlp|5 years ago