wren/test at 19fc5e75344bd3600fe23661163c15adb9a783e0 - wren

Files

T

Bob Nystrom f16e5c775f feat: report undefined variable errors on the line where they are used

Store the line number of first use in implicitly declared variables as a numeric value, then synthesize a token at that line when reporting the error, ensuring bounded error message length even for pathologically long variable names.

2016-03-16 15:00:28 +00:00

api

test: add test for creating a VM with null config and fix wrenNewVM to handle NULL config

2016-03-03 22:31:47 +00:00

benchmark

feat: add wrenGetValueDouble API and benchmark for wrenCall() performance

2015-12-24 01:29:53 +00:00

core

feat: unify Fiber.try() error messages with call/transfer by adding verb parameter to runFiber

2016-03-04 01:00:33 +00:00

feat: add File.realPath() to resolve symlinks and normalize paths

2016-02-27 23:53:02 +00:00

language

feat: report undefined variable errors on the line where they are used

2016-03-16 15:00:28 +00:00

limit

fix: add overflow check for jump distance in patchJump and emit error on too much code

2016-02-19 14:57:38 +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.