wren/test at 6a56bd2ee92c5f45f6e4a0eea3d98090120b39be - wren

Files

T

Bob Nystrom 6a56bd2ee9 feat: add binary_trees_gc benchmark that explicitly invokes System.gc

Add a new benchmark variant of the binary_trees test that calls System.gc() after
each tree construction phase to measure garbage collection overhead. The benchmark
creates a stretch tree, a long-lived tree, and iterates through depths 4 to 12
with explicit GC calls between iterations. Register the new benchmark in
util/benchmark.py with expected output values matching the original binary_trees
benchmark.

2015-10-24 18:00:17 +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

fix: close only existing upvalues for locals in scope during stack unwinding

2015-10-08 15:06:29 +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.