cea71c2fe4
The previous GC implementation used a recursive mark method. This can result in stack overflows when attempting to mark deeply nested objects. This commit replaces the recursive approach with an iteritive one, moving the state stack from the C call stack to the `WrenVM` structure. As objects are 'grayed' they are pushed onto the VM's gray stack. When we have grayed all of the root objects we iterate until the stack is empty graying any obejcts which haven't been marked as dark before. At the end of the process we clean up all unmarked objects as before. This commit also adds a few new tests which check garbage collection by allocating some new deeply nested objects and triggering the GC a few times in the process.
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.