wren/test at 419a5dfda0a3521d8ad6ac222764a50447f8fc8e - wren

Files

T

Bob Nystrom 21c5611bf0 fix: close only existing upvalues for locals in scope during stack unwinding

The previous implementation unconditionally closed the first open upvalue when
executing CLOSE_UPVALUE, which could crash when a local variable was never
actually captured by a closure. Changed closeUpvalue to closeUpvalues with a
stack threshold parameter, so only upvalues whose stack slot is at or above the
given pointer are closed. This prevents closing nonexistent upvalues for locals
that were never closed over, fixing segfaults in unused closure scenarios.

Added regression tests for unused closures and for nested scopes where only
some locals are captured.

2015-10-08 15:06:29 +00:00

api

feat: add va_list version of wrenCall and fix GC bug with return values

2015-09-30 02:29:10 +00:00

benchmark

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

2015-09-15 14:46:09 +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

io/file

feat: implement async file I/O with open/close/readBytes and scheduler error handling

2015-10-01 04:13:36 +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.