<@U0HUJ25V1> We had such ranges in mind: so before...

# stdlib

[ilya.gorbunov]

@thomasnield We had such ranges in mind: so before 1.0 we had renamed Range to ClosedRange and its end property to endInclusive and dropped FloatRange and DoubleRange to make it possible to introduce open-ended ranges without breaking changes later.

[thomasnield]

So are y'all just waiting for use cases to justify them? If so, I can put them together and file a KEEP or issue.

[thomasnield]

Starting a KEEP. Not sure what the best way is to invoke an exclusive range.

The start..end operator is already reserved for inclusive ranges. Maybe (start..end).endExclusive() would be the best way to construct an end exclusive range?