wren/test at 9fe0b2475eb81778c941d8ea7f90ea3e58d74d99 - wren

Files

T

Bob Nystrom ee2789dea7 perf: replace single gc calls with 1000-iteration loops in binary_trees_gc benchmark

In the binary_trees_gc.wren benchmark, change each of the three single System.gc() calls to a for loop that invokes System.gc() 1000 times, increasing garbage collection pressure during tree construction and traversal phases.

2015-10-28 14:46:06 +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

fix: increase GC stress in binary_trees_gc benchmark by calling gc 1000 times per cycle

2015-10-28 14:45:52 +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.