Re:What's New in Lua 5.4
by pwdisswordfish2 on Thursday July 16, 2020 @03:26AM
(#23856670)
Thing is, end-exclusive ranges go hand-in-hand with zero-based indexing. I don’t think I need to link the EWD article.
I don't find it particularly persuasive. End-exclusive and end-inclusive can both be natural in different scenarios, regardless of the base - the article simply cherry-picks the ones that it needs to "prove" its case. That's why it's best when the language just offers both.
> Nim almost gets there: (x .. y) is end-inclusive, and (x ..< y) is end-exclusive - but the syntax still exhibits a preference.
Swift is similar, using `...` and `..<`. Rust uses an alternative convention, `..=` and `..`.
Would you prefer to see `..=` and `..<` so that inclusivity/exclusivity is always explicit?
Yep, pretty much. I'm a strong proponent of "explicit is better than implicit" in all cases where there's no default that's obviously preferable, and this is is one of those cases - that different languages picked different defaults is all the evidence I need.
FWIW, I think that the real mistake was to make inclusivity/exclusivity implicit to begin with. If the syntax is explicit, and the choice is captured in the resulting value (i.e. it's more than just a pair of numbers), then you just use whatever is more convenient for the task at hand. Nim almost gets there: (x .. y) is end-inclusive, and (x ..< y) is end-exclusive - but the syntax still exhibits a preference.