wren/test at 372cd3e1979d51385dddf690047ce637e2115bb6 - wren

Meson/wren

Files

Bob Nystrom 2c88e19497 Compile imports to closures, not fibers.

This is simpler and marginally faster. We don't need the overhead of
fibers since you can't have long or recursive import chains anyway.

More importantly, this makes the behavior more well-defined when you do
things like yield from an imported module. (Not that you should do that,
but if you do, it shouldn't do weird things.)

2018-03-17 09:33:33 -07:00

api

Add test for user data.

2017-03-22 07:26:19 -07:00

benchmark

Add a benchmark for wrenCall().

2015-12-23 17:29:53 -08:00

core

Compile imports to closures, not fibers.

2018-03-17 09:33:33 -07:00

Add Stdin.isTerminal.

2016-05-21 12:51:11 -07:00

language

Use strtoll() for hex literals to handle 64-bit ones even on 32-bit.

2017-01-12 21:53:21 -08:00

limit

Use a map to check for constant collisions.

2016-08-16 07:43:34 -07: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.