Idea: RangeFrom

[CAD97]

If we reserve u32::MAX to mean unbounded, we can have TextRange::from(size) => size.. and TextRange::to(size) => 0..size. (The lower unbound can just be immediately normalized to 0.)

[matklad]

TextRange::from(size)

This is objectively horrible, because it's not From::from :)

[CAD97]

yeah I realize that now but ignore the naming is the underlying concept good/bad/meh/worth-it/not

[matklad]

Another problem with treating u32 as unbounded is that it adds semi-infitite ranges. And that makes usages of TextRange harder: even len then should return an Option<TextSize>.

[CAD97]

Still, one of the main uses of the TextUnit->usize escape hatch in ra is RangeFrom... if only we could let string[TextSize..] work... SliceIndex is actually stable, it's just sealed. I asked about it, but obviously an implementable SliceIndex is a while away even if desirable.