wren/test at f2077844b3a37f10e75e389ec7f7b32e0d370321 - wren

Files

T

Bob Nystrom 4d1215697e feat: add MapEntry class and make Map a Sequence for direct iteration

Add MapEntry class to expose key-value pairs during map iteration, and make Map extend Sequence so maps can be directly iterated with `for` loops. Rename the internal `iterate_` primitive to `iterate` and update error messages for invalid map iterators.

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

api

feat: add wrenAbortFiber() API to abort current fiber with runtime error object

2016-06-10 02:14:21 +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.