wren/test at 5d04ed2aedb19b529ddc9cd3a636e2c132f7248a - wren

Files

T

Bob Nystrom 5d04ed2aed fix: add overflow check for jump distance in patchJump and emit error on too much code

Add a MAX_JUMP constant set to 2^16 and validate jump distance in patchJump to prevent silent overflow when bytecode exceeds the maximum representable offset. Also remove the TODO comment in endLoop since the forward jump error will be caught by patchJump. Include test cases jump_too_far.wren and loop_too_far.wren to verify the compiler correctly reports "Too much code to jump over." for both conditional and loop constructs.

2016-02-19 14:57:38 +00:00

api

feat: replace wrenAllocateForeign with wrenSetSlotNewForeign supporting arbitrary slot and class selection

2016-01-24 17:25:04 +00:00

benchmark

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

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

core

fix: remove fiber support as map keys and revert to value-only key validation

2015-12-15 18:42:21 +00:00

feat: move File.stat to Stat.path and update all references across docs, source, and tests

2016-02-07 17:56:16 +00:00

language

feat: allow call and unary expressions as map keys in compiler

2015-12-23 00:00:50 +00:00

limit

fix: add overflow check for jump distance in patchJump and emit error on too much code

2016-02-19 14:57:38 +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.