Introduce a new static method `Object.same(obj1, obj2)` that exposes the VM's built-in equality semantics (`wrenValuesEqual`) directly, bypassing any user-defined `==` overrides. This required creating a dedicated metaclass for Object (subclass of Class) to host the static method without polluting every class with a `same` method. The implementation wires up a new `Object metaclass` in the core initialization sequence, adjusts the class hierarchy setup order, and adds comprehensive tests covering value types, identity comparison, and verification that `Object.same` ignores custom `==` operators.
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. -
io/- Tests for the built in IO library. In other words, methods on theIOclass. If a bug is inwren_io.c, it should 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.