wren/test at 5f8794fdc2c3eacef5c00343aa7ce61a15ce3a8f - wren

Files

T

Bob Nystrom 5f8794fdc2 refactor: rename list C API functions and remove Slot suffix for consistency

- Rename wrenGetSlotListSize to wrenGetListCount and wrenGetSlotListValue to wrenGetListElement
- Change wrenGetListElement to move element directly to another slot instead of returning WrenValue
- Update all test bindings and calls to match new API signatures

2016-07-28 15:06:36 +00:00

api

refactor: rename list C API functions and remove Slot suffix for consistency

2016-07-28 15:06:36 +00:00

benchmark

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

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

core

feat: add MapEntry class and make Map a Sequence for direct iteration

2016-07-06 14:17:07 +00:00

feat: add Stdin.isTerminal method to detect TTY connection

2016-05-21 19:51:11 +00:00

language

feat: implement expression evaluation and statement detection in REPL with Meta.compileExpression

2016-05-21 06:03:05 +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.