| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Lua 5.2 only used the __eq metamethod if both operands have the same
__eq, but Lua 5.3 will pick one from either operands that has one as
long as both are tables.
This results in array() == {} and all sorts of odd behavior, including
array() == util.json.null.
<MattJ> I think [array() == {}] should have the same semantics as {} == {}
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
return them in a table at the end
|
| |
|
|
|
|
| |
non-mutating function
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
their names suggested
|
| |
|
|
|
|
| |
var to be preserved
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
mutated copy, and most methods (e.g. sort) now return the array
|
| |
|
|
|
|
| |
joined
|
|
|
|
| |
allow chaining
|
| |
|
|
|
|
| |
array, and use module() to correctly set the module name
|
| |
|
| |
|
|
|