Yeah, 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. :-)
Re:Up to 4GB of Memory in WebAssembly
by steveklabnik on Friday May 15, 2020 @05:21PM
(#23197587)
There is no plans at this time, but I'm always interested in hearing what folks have to say...
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.