[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: ipairs iterator overflowing
- From: Halalaluyafail3 <luigighiron@...>
- Date: Sat, 11 Sep 2021 16:07:25 -0400
Lua 5.4 changed the semantics of integer for loops to end the loop in
the case of overflow. This means that a construct like "'for i=1,#t"
will always work, even if #t is the maximum integer. The ipairs
iterator function doesn't have similar semantics, instead when the
second argument to the iterator function is the maximum integer it
will overflow and cause undefined behavior.
Following the semantics of the integer for loop, I think it would make
the most sense to return nil in the case of the second argument being
the maximum integer, instead of overflowing and causing undefined