2 ms·
We did option 3, and it made examples and docs very difficult. Option 1 is not acceptable given Rust's attitude towards allocation. We could do option 2, it's
by steveklabnik 7y ago
We did option 3, and it made examples and docs very difficult.
Option 1 is not acceptable given Rust's attitude towards allocation.
We could do option 2, it's true.
> The rationale for i32 in RFC 0212 is basically, "well C compilers usually do this"
I don't agree with this; but it doesn't really matter at the end of the day, it's been years and this can't really change.
Regardless, I appreciate the elaboration :) It helps me understand the way others think about Rust.
- xscott 7y agoYeah, I realize none of this can change. However, if there is ever a breaking version 2.0 on the roadmap, I'll tell you the features which keep me from actually using Rust. The i32 is pretty insignificant. :-)
- steveklabnik 7y agoThere is no plans at this time, but I'm always interested in hearing what folks have to say...