A dynamically typed Lua value. The
variants contain handle types into the internal Lua state. It is a logic error to mix handle
types between separate
Lua instances, and doing so will result in a panic.
The Lua value
The Lua value
A “light userdata” object, equivalent to a raw pointer.
An integer number.
Any Lua number convertible to a
Integer will be represented as this variant.
A floating point number.
A Luau vector.
An interned string, managed by Lua.
Unlike Rust strings, Lua strings may not be valid UTF-8.
Reference to a Lua table.
Reference to a Lua function (or closure).
Reference to a Lua thread (or coroutine).
Reference to a userdata object that holds a custom type which implements
Special builtin userdata types will be represented as other
Error is a special builtin userdata type. When received from Lua it is implicitly cloned.
Compares two values for equality.
Equality comparisons do not convert strings to numbers or vice versa. Tables, Functions, Threads, and Userdata are compared by reference: two objects are considered equal only if they are the same object.
If Tables or Userdata have
__eq metamethod then mlua will try to invoke it.
The first value is checked first. If that value does not define a metamethod
__eq, then mlua will check the second value.
Then mlua calls the metamethod with the two values as arguments, if found.
Converts the value to a generic C pointer.
The value can be a userdata, a table, a thread, a string, or a function; otherwise it returns NULL. Different objects will give different pointers. There is no way to convert the pointer back to its original value.
Typically this function is used only for hashing and debug information.
Returns the argument unchanged.