wren/test at 6b40c5b3f5852ed7fed7f5892592fe151822d65d - wren

Files

T

Bob Nystrom 7e111d19da feat: replace fiber run() with transfer() and suspend() for scheduler-friendly semantics

Remove the run() method from fibers and introduce transfer() for non-stack-based fiber switching, along with suspend() to pause the interpreter and return control to the host application. Update Timer.sleep() to use runNextScheduled_() instead of Fiber.yield(), and add Timer.schedule() for creating independently scheduled fibers. Refactor the core fiber runtime to support transfer semantics, including proper error handling for aborted fibers and self-transfer edge cases. Fix a missing quote in test.py's runtime error validation string.

2015-08-31 05:15:37 +00:00

api

feat: add foreign class support with allocation, construct opcodes, and CLI callback wiring

2015-08-15 19:07:53 +00:00

benchmark

feat: add Alexander Roper to AUTHORS and expand embedding API documentation

2015-08-29 06:13:56 +00:00

core

feat: replace fiber run() with transfer() and suspend() for scheduler-friendly semantics

2015-08-31 05:15:37 +00:00

chore: migrate Travis CI to container-based builds and update README links

2015-07-19 19:49:23 +00:00

language

fix: correct test name from 'should_process_empty_input' to 'should_handle_empty_input'

2015-08-21 05:04:42 +00:00

limit

feat: replace 'this' keyword with 'construct' for constructor definitions across core lib, compiler, docs, and tests

2015-07-21 14:24:53 +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.
io/ - Tests for the built in IO library. In other words, methods on the IO class. If a bug is in wren_io.c, it should 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.