wren/test at 8fd9449196894d6af4e7924107a93882d4a29183 - wren

Files

T

Bob Nystrom 8fd9449196 feat: implement async file I/O with open/close/readBytes and scheduler error handling

Add foreign class File with static open, read, size methods and instance methods for close, size, readBytes. Implement async file operations using libuv callbacks that resume fibers on completion. Introduce schedulerResumeError and resumeError_ to propagate I/O errors as fiber errors. Add setExitCode to CLI vm for runtime error exit handling. Bump MAX_METHODS_PER_CLASS from 2 to 9 to accommodate new File methods.

2015-10-01 04:13:36 +00:00

api

feat: add va_list version of wrenCall and fix GC bug with return values

2015-09-30 02:29:10 +00:00

benchmark

feat: replace IO class with System class and remove separate IO module

2015-09-15 14:46:09 +00:00

core

feat: add isInfinity and isInteger methods to Num class

2015-09-30 15:41:43 +00:00

io/file

feat: implement async file I/O with open/close/readBytes and scheduler error handling

2015-10-01 04:13:36 +00:00

language

feat: allow super calls in static methods by removing compiler error and fixing metaclass binding

2015-09-19 22:19:41 +00:00

limit

feat: replace IO class with System class and remove separate IO module

2015-09-15 14:46:09 +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.