>This seems to me to just be an unfixable design flaw due to backwards-compatibility rules
This sounds like something that could be solved in the next edition.
How?
Make the (x..y) syntax construct some std::BetterRange for code in a new edition.
I don't really get where you're coming from here, especially with regards to this issue -- it seems like almost everyone, including Rust core team members, agree that `impl Iterator for Range` was an API design mistake, that came out of (IIRC) Iterator existing prior to IntoIterator in the pre-1.0 days. This seems to me to just be an unfixable design flaw due to backwards-compatibility rules, not something that really speaks to the design of the language as a whole.