This is one of the things that improved in Lua 5.4. Now it caches the table length so that the # operator is O(1) in many common situations.
That is, does #({[1]="a", [3]="b"}) return 1 or 2?
edit: I see that it still returns 1. That's a shame. This trips up so many newcomers who've been told that "#" means "length". IMO they need to either start calling it something other than the "length operator" or make it _actually_ return the length. Sadly at this point it would just be yet another breaking change.
edit: yes, in fantasy-lua there will be an array type that can represent [1,nil,3] (sequence of 3 values)
Some early alpha versions of Lua 5.4 played around with this idea but it turns out that it would break too many things. I'd expect that if Lua ever makes a major jump to Lua 6.0 then nils in tables will likely be one of the main changes.
On the other hand, my not-very-well-considered preferred approach creates some asymmetry between arrays and maps as to what values can be stored. Or it perpetuates the existing asymmetry between varargs and tables...
> t[i]=undef is a special syntax form that means "remove the key 'i' from table 't'". You can only use 'undef' in three specific forms:
t[i] = undef -- remove a key from a table
t[i] == undef -- test whether a table has a key
t[i] ~= undef -- test whether a table has a key
That's not what string.sub accepts though.
> Plus, between the operations of "get final index" and "split interval into non-overlapping pieces", "get final index" is far more common (it's crucial to stacks, queues, etc, in addition to various uses like iterating backwards). Choosing "closed" intervals is then the cleaner option to avoid an ugly "+" or "-"!
It (rather unnecessarily) takes log time, so you probably shouldn't do it if you can avoid it.