wren/test at 3b448427fb5767222b377fdc92faf2304843efa6 - wren

Files

T

Andew Jones 3b448427fb fix: propagate error through nested fiber callers in try blocks

Move the aborted fiber check before the already-called check in runFiber to catch errors earlier. In runtimeError, walk the caller chain to find the nearest fiber with callerIsTrying set, properly propagating errors through nested fiber calls. Add test cases for two and three levels of nested fiber try blocks.

2017-03-31 01:57:29 +00:00

api

test: add wrenSetSlotNull call and verify slot type in setSlots test

2017-03-03 15:57:50 +00:00

benchmark

feat: add wrenGetValueDouble API and benchmark for wrenCall() performance

2015-12-24 01:29:53 +00:00

core

fix: propagate error through nested fiber callers in try blocks

2017-03-31 01:57:29 +00:00

feat: add Stdin.isTerminal method to detect TTY connection

2016-05-21 19:51:11 +00:00

language

fix: replace strtol with strtoll for 64-bit hex literal parsing on 32-bit platforms

2017-01-13 05:53:21 +00:00

limit

perf: replace O(n) linear scan with O(1) map lookup for constant deduplication in compiler

2016-08-16 14:43:34 +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.