13 ms·
This is the difference between "simple" and "easy", as Rich Hickey so eloquently put it. C--this part of it, at least--is easy. You can write code without havin
by pcwalton 5y ago
This is the difference between "simple" and "easy", as Rich Hickey so eloquently put it. C--this part of it, at least--is easy. You can write code without having to think about the different integer types, thanks to the complex integer promotion rules. Rust and Go are simple: the semantics are clear and understandable, at the cost of requiring the programmer to think about this aspect of numeric types. As programmers, we often mistakenly think that simple decisions automatically lead to an easy interface for the user; sometimes they do, but not always.
(On balance, I personally think that not having the implicit conversions, as Rust and Go do, is generally the better decision, but I certainly acknowledge that C is easier in this regard.)
- pasabagi 5y ago> (On balance, I personally think that not having the implicit conversions, as Rust and Go do, is generally the better decision, but I certainly acknowledge that C is easier in this regard.) Really? I think there must be a better way - I also don't like implicit conversions, but the rust approach gets extremely verbose, especially if you want to check for truncation etc.