wren/test at 10a0a700544f649353f37d1955ab55c910c5c5ef - wren

Files

T

Sven Bergström 98e74d560e fix: guard against local variable array overflow in for-loop hidden variables

Add bounds check in forStatement to ensure compiler->numLocals + 2 does not exceed MAX_LOCALS before calling addLocal for the hidden 'seq ' and iterator variables. Includes regression test with deeply nested for-loops that previously caused an array overflow.

2019-09-18 07:20:03 +00:00

api

fix: check for fiber error after foreign class allocation to support wrenAbortFiber

2019-09-17 17:43:53 +00:00

benchmark

fix: replace hashBits with V8's integer hash to fix catastrophic collision for numeric keys

2019-07-27 20:34:07 +00:00

core

feat: add String.fromByte primitive with validation and unit tests

2019-02-27 13:05:07 +00:00

feat: add Stdin.isTerminal method to detect TTY connection

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

language

feat: add placeholder file to force Git tracking of empty modules directory

2018-07-24 14:15:04 +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.