wren/test at c5befa72cfda8c8e35d405946ae33cc95121e206 - wren

mirror of https://github.com/wren-lang/wren.git synced 2026-01-11 14:18:42 +01:00

Files

Bob Nystrom c5befa72cf Don't use module import string when loading imported variables.

This is an interim step towards supporting relative imports. Previously,
the IMPORT_VARIABLE instruction had a constant string operand for the
import string of the module to import the variable from. However, with
relative imports, the import string needs to be resolved by the host
all into a canonical import string. At that point, the original import
string in the source is no longer useful.

This changes that to have IMPORT_VARIABLE access the imported ObjModule
directly. It works in two pieces:

1. When a module is compiled, it ends with an END_MODULE instruction.
   That instruction stores the current ObjModule in vm->lastModule.

2. The IMPORT_VARIABLE instruction uses vm->lastModule as the module to
   load the variable from. Since no interesting code can execute between
   when a module body completes and the subsequent IMPORT_VARIABLE
   statements, we know vm->lastModule will be the one we imported.

2018-03-20 06:54:51 -07:00

api

Don't use module import string when loading imported variables.

2018-03-20 06:54:51 -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.