wren/test at ba0d308fba9bb36c91b1d9865f52cad50c8e2d93 - wren

Files

T

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

The previous implementation allowed fibers as map keys by assigning each fiber a unique numeric ID for hashing and equality. This was originally added to support a misguided attempt at thread-local storage that was never used. This commit removes the fiber ID field from ObjFiber, the nextFiberId counter from WrenVM, the fiber hashing case in hashObject(), and the IS_FIBER check in validateKey(). The error message for invalid keys is updated from "Key must be a value type or fiber." to "Key must be a value type." and all affected test expectations are updated accordingly.

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

api

feat: implement string interpolation with %(expr) syntax in compiler and core library

2015-11-11 15:55:48 +00:00

benchmark

fix: correct fiber count in benchmark comment from 10000 to 100000

2015-12-15 18:37: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: implement string interpolation with %(expr) syntax in compiler and core library

2015-11-11 15:55:48 +00:00

language

fix: propagate compile errors from imported modules and update test runner to skip them

2015-12-08 15:49:37 +00:00

limit

feat: implement string interpolation with %(expr) syntax in compiler and core library

2015-11-11 15:55:48 +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.