wren/test at 810da1f0fc38d620818eae56939100f56c5d7956 - wren

Files

T

Bob Nystrom 810da1f0fc feat: add libuv event loop integration with timer module and CLI restructuring

Add a vertical slice of real libuv integration by introducing a "timer" CLI module with a Timer class and static sleep() method. This required significant infrastructure changes: setting up libuv event loop in the CLI, creating a new src/module directory for CLI modules, updating all build scripts (Makefile, wren.mk, Xcode project) to handle the new module compilation, and reorganizing CLI code by moving REPL logic from main.c to vm.c. The generate_builtins.py script was also updated to support copying Wren sources into the module directory.

2015-08-07 15:10:55 +00:00

api

feat: add libuv event loop integration with timer module and CLI restructuring

2015-08-07 15:10:55 +00:00

benchmark

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

2015-07-21 14:24:53 +00:00

core

fix: correct tombstone handling in map insertion to prevent deadlock

2015-08-06 13:55:30 +00:00

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

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

language

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

2015-07-21 14:24:53 +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.