News for hackers. Stuff that matters.
Re:My least favorite Rust type by coolreader18 on Monday September 21, 2020 @07:59PM (#24549635)
> I get a strong sense of Rust demanding that users subjugate themselves to all the choices and opinions of the architects [..]

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.

Re:My least favorite Rust type by carlmr on Tuesday September 22, 2020 @04:29AM (#24552223)
>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.

Re:My least favorite Rust type by timClicks on Tuesday September 22, 2020 @05:33AM (#24552586)
How?
Re:My least favorite Rust type by floatboth on Tuesday September 22, 2020 @06:36AM (#24552930)
Make the (x..y) syntax construct some std::BetterRange for code in a new edition.
Re:My least favorite Rust type by timClicks on Wednesday September 23, 2020 @06:14AM (#24565188)
But wouldn't that lead to backwards incompatibilities?