The compiler now always reserves slot zero for either the closure or method receiver, eliminating a corner case where top-level REPL code lacked the pre-allocated slot that function/method bodies expect. This ensures local variables declared in REPL loops (e.g. `for (i in 1..2)`) get correct slot indexes. Additionally, inlines `wrenResetFiber` into `wrenNewFiber` and stores the imported module's closure on the stack before invoking it, preventing a GC from collecting the closure during import.
This contains the automated validation suite for the VM and built-in libraries.
-
benchmark/- Performance tests. These aren't strictly pass/fail, but let us compare performance both against other languages and against previous builds of Wren itself. -
core/- Tests for the built in core library, mainly methods on the core classes. If a bug is inwren_core.corwren_value.c, it will most likely break one of these tests. -
language/- Tests of the language itself, its grammar and runtime semantics. If a bug is inwren_compiler.corwren_vm.c, it will most likely break one of these tests. This includes tests for the syntax for the literal forms of the core classes. -
limit/- Tests for various hardcoded limits. The language doesn't officially specify these limits, but the Wren implementation has them. These tests ensure that limit behavior is well-defined and tested.