3 ms·
Then just define a type alias, which is good practice if you want your types to be more descriptive: https://doc.rust-lang.org/reference/items/type-aliases.html
by pezezin 2y ago
Then just define a type alias, which is good practice if you want your types to be more descriptive: https://doc.rust-lang.org/reference/items/type-aliases.html https://doc.rust-lang.org/reference/items/type-aliases.html
- kazinator 2y agoNope! Because then you will also define an alias, and Suzy will define an alias, and Bob will define an alias, ... We should all agree on int and uint; not some isize nonsense, and not bobint or suzyint.
- jclulow 2y agoAlas, it's pretty clear that we won't!
- pezezin 2y agoOk, it is obvious that you are looking for something to complaint about and don't want to find a solution. That is not a productive attitude in life, but whatever floats your boat. Have a good day.
- kazinator 2y ago> looking for something to complaint about You know, that describes pretty much everyone who has anything to do with Rust. "My ls utility isn't written in Rust, yikes! Let's fix that!" "The comments under this C++-related HN submission aren't talking about Rust enough, yikes! Let's fix that!" I'm obviously pointing to a solution: have a standard module that any Rust program can depend on coming from the language, which has a few sanely named types. Rather than every program defining its own.
- hahamaster 2y agoYou insist that we should all agree on something but you don't specify what.