wren/test at dbd75f8905fd712fe69881a58072a8ea5760ee47 - wren

Files

T

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

Change the map key parsing precedence from PREC_PRIMARY to PREC_UNARY in
wren_compiler.c, enabling method calls (e.g., name.count), subscript
access (name[0]), and unary operators (-1, ~3) as valid map keys.

Add two test files: precedence.wren verifying the new key types work
correctly, and bad_key_precedence.wren confirming that binary operators
like addition still produce a parse error.

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

api

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

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