Description
The issue I'd like to address was discussed and closed ten years ago in #9555.
I wonder how many people have come across it.
I see the point, I understand the benefits of having this particular behaviour!
However, the fact that there isn't any algorithm still, stating that Rust's range is different from ranges in other languages makes me raise this matter again.
My proposition is to include a warning, for expicit norage ( uInt..0 )
so a for i in uInt..0 {}
may triger:
Warning: Unused block of code
or
Note: Rust range (start..end) if and only start < end
or
Help: If you meant to iter over revers range use (0..uInt).rev()
anything but silence really!
It looks like something unimportant but silencing an explicit dead block of code it is not what's expected from an environment
which casually warns about unused variables, this is not why we love Rust so much: