3 ms·
I work with Lua extensively, including abstract syntax trees. To mark a node at the third position, containing one character, we say {3,3}. But what if there'
by samatman 6y ago
I work with Lua extensively, including abstract syntax trees.
To mark a node at the third position, containing one character, we say {3,3}.
But what if there's a node at the third position, that contains no character? Well, thats {3,2}.
It's like nails on a chalkboard every time. 1-based indexing is a mistake.
~=, by contrast, is just notation. You get used to it quickly.
- saagarjha 6y ago> To mark a node at the third position, containing one character, we say {3,3}. > But what if there's a node at the third position, that contains no character? Well, thats {3,2} Why not shift over indexing by one consistently? So you'd use {3, 4} and {3, 3} for each, so the length property is preserved.
- samatman 6y agoBecause that's not how the string library works. ("12345"):sub(3,3) returns "3", while ("12345"):sub(3,4) returns "34", and ("12345"):sub(3,2) returns "". Indexing in the array portion of tables, and strings, is at least consistent; but Djikstra was right. The Wiki[0] has a good discussion of Djikstra's iconic essay. The best of these arguments, imho: 0 based indexing unifies enumeration and measurement. [0]: https://wiki.c2.com/?WhyNumberingShouldStartAtZero https://wiki.c2.com/?WhyNumberingShouldStartAtZero
- int_19h 6y agoThat's an argument against end-inclusive ranges more so than against 1-based indexing. If they were end-exclusive, like in Python, then {3,3} would be an empty string, and {3,4} would be a single character at 3. Note how it suddenly doesn't matter at all whether the indices are 0-based or 1-based - all of the above is valid regardless. 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.
- pwdisswordfish2 6y agoThing is, end-exclusive ranges go hand-in-hand with zero-based indexing. I don’t think I need to link the EWD article.
- int_19h 6y agoI 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.
- pansa2 6y ago> 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?
- int_19h 6y agoYep, 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.