Re: Changing tables during traversal: clearing and re-adding a field

[Rebel Neurofog <rebelneurofog@...>]

>> I see the point now. Undefined behavior is undefined behavior.
>> On the other hand, why not define it in a different way?
>> [...]
>
> I think the current rules are already too complex...
>

Perhaps, you are right.
And I'd like to notice that this way of understanding is
what my intuition told me about EXISTING version of Lua.

So I guess, the way you pointed me:

> See the code: When it does t[k] =<some other value>, the field t[k] does
> not exist (it was erased two lines earlier), so it is assigning to a
> non-existent field, which is explicitly forbiden.

should somehow be explicitly noted in reference manual.