wren/test at 5865f534fc369538735e83061b9c80802d2851d0 - wren

Files

T

Bob Nystrom 5865f534fc fix: change map key parsing precedence from PRIMARY to UNARY

In wren_compiler.c, the map() function now parses map keys with PREC_UNARY
instead of PREC_PRIMARY, allowing unary operators like negation and bitwise
NOT in key expressions. Added test/language/map/bad_key_precedence.wren to
verify that binary operators (e.g., 1 + 2) still produce an error when used
as keys, and test/language/map/precedence.wren to validate correct parsing
of primary, call, and unary expressions in map keys.

2015-12-23 17:22:49 +00:00

api

feat: add wrenEnsureSlots, wrenSetSlotNewList, and wrenInsertInList C API functions for list manipulation

2015-12-17 00:28:26 +00:00

benchmark

feat: add benchmark for Wren C API foreign method calls and refactor test class names

2015-12-16 00:02:13 +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

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

2015-12-23 00:00:50 +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.