wren/test at 140fb7738e24e382b28c73d2ef1e7671a85bb5d0 - wren

Files

T

Will Speak 140fb7738e feat: replace recursive mark with iterative gray/darken GC to prevent stack overflow

The previous recursive `wrenMarkObj` approach could overflow the C stack when marking deeply nested object graphs. This commit introduces an iterative two-phase collector: objects are first "grayed" onto an explicit stack in the WrenVM struct, then `wrenDarkenObjs` iteratively processes the gray stack until all reachable objects are marked as "dark". The `marked` field is renamed to `isDark` to reflect the new semantics. A `gray` array with `grayDepth` and `maxGray` tracking is added to `WrenVM`, initialized in `initializeGC` and freed in `wrenFreeVM`. All internal mark calls (`markClass`, `markClosure`, `markFiber`, `wrenCollectGarbage`) are updated to use `wrenGrayObj` instead of `wrenMarkObj`. Two new test files (`deeply_nested_gc.wren` and `many_reallocations.wren`) verify that deeply nested object graphs and repeated GC cycles complete without stack overflow.

2015-10-19 21:45:15 +00:00

api

feat: add System.gc() method and replace test's Api.gc() with it

2015-10-24 17:56:27 +00:00

benchmark

feat: add binary_trees_gc benchmark that explicitly invokes System.gc

2015-10-24 18:00:17 +00:00

core

feat: remove PRIM_CALL result type and add METHOD_FN_CALL for function call special-casing

2015-10-04 02:04:11 +00:00

feat: add Stdin class with readLine and async stdin read support in io module

2015-10-17 04:05:24 +00:00

language

feat: replace recursive mark with iterative gray/darken GC to prevent stack overflow

2015-10-19 21:45:15 +00:00

limit

feat: replace IO class with System class and remove separate IO module

2015-09-15 14:46:09 +00:00

README.md

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 in wren_core.c or wren_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 in wren_compiler.c or wren_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.