wren/test at 8210452970eaa2e25c1a1a68318553a11f65b317 - wren

Files

T

Bob Nystrom 8210452970 Relative imports!

This is a breaking change because existing imports in user Wren code
that assume the path is relative to the entrypoint file will now likely
fail.

Also, stack trace output and host API calls that take a module string
now need the resolved module string, not the short name that appears in
the import.

2018-03-24 11:10:36 -07:00

api

Relative imports!

2018-03-24 11:10:36 -07:00

benchmark

Add a benchmark for wrenCall().

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

core

Relative imports!

2018-03-24 11:10:36 -07:00

Add Stdin.isTerminal.

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

language

Relative imports!

2018-03-24 11:10:36 -07: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.