Canonicalize APIs around `Int`

I already replied in the other thread: `Indexer` and `Int` vs `UInt` - #157 by owenhilyard

I will would like to, once again, state that Rust should have the worst possible version of the problem Swift is talking about here, since it forces explicit casts for everything and has an integer type which is basically only used for indexing. Even before the removal of implicit IntUInt casts, the top 1000 Rust crates had a lower density of casts than both the Mojo stdlib and MAX. To me, this indicates there is a solution to that problem which doesn’t sacrifice using “the most specific type” for integers, which I suspect is closely related to not having a type called Int.

2 Likes