Sam Sung c97fd03a57 Lua tables, ipairs and globals behave as the client's 5.0 (#1792) ...

benilla-lua's tables and globals now follow the client's Lua 5.0, not 5.1.

Tables:
- They size, fill and rehash as 5.0's ltable.c does: the hash part doubles (`0x6fab90`), and a log size of 0 is the shared dummy (`0x6fa601`).
- A hash part past 2^24 nodes raises `table overflow`.
- Constructors store every 32 items.
- A weak table's clearing removes the key, so `next` from it raises (`0x6f79d0`).
- A weak-keyed table keeps its string keys (`0x6f79f0`).

Globals and libraries:
- `ipairs` returns itself, and a second argument steps once.
- `setglobal` assigns the top of the stack.
- The state opens in the client's order, with no `_G`.

Each new test fails without its fix.

Fixes #1487
Fixes #1789
Fixes #1790
Fixes #1169

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-17 17:49:05 +07:00

..

examples

benilla-lua's VM and compiler behave as the client's Lua 5.0 (#1768)

2026-10-17 11:07:05 +07:00

src

Lua tables, ipairs and globals behave as the client's 5.0 (#1792)

2026-10-17 17:49:05 +07:00

tests

Lua tables, ipairs and globals behave as the client's 5.0 (#1792)

2026-10-17 17:49:05 +07:00

Cargo.toml

Run the script host on benilla-lua; remove the vendored C Lua and mlua (#1255)

2026-10-17 08:51:37 +07:00

GRAMMAR.md

benilla-lua's VM and compiler behave as the client's Lua 5.0 (#1768)

2026-10-17 11:07:05 +07:00