Contradiction in RFC1192 (Inclusive Ranges) #1537
Description
The "Detailed design" section mentions
Writing ...b in an expression desugars to std::ops::RangeToInclusive { end: b }.
However, the "Alternatives" sections states
This RFC doesn't propose non-double-ended syntax, like a..., ...b or ... since it isn't clear that this is so useful. Maybe it is.
From what I have gathered, the specified design has been implemented.