Re: Strange Lua behavior with __eq return values

["Alex Davies" <alex.mania@...>]

Definitely a manual problem.

Imo the current behaviour is more "correct", as it means people won't get 
caught off-guard when they return a value instead of double notting it 
first.

(Just to explain the current behaviour, Lua always compiles:

local bool = a == b

to this:

local bool;
if a == b then
 bool = true
else
 bool = false
end

- There is no "SETEQ" opcode.)