wren/test at bd0957dc4824c3d57d563a19b30a91661b8887fe - wren

Files

T

Bob Nystrom bd0957dc48 fix: double delta_blue benchmark iterations and update expected result

The delta_blue benchmark was updated to run 40 iterations instead of 20 in both the Python and Wren implementations, and the expected benchmark result was adjusted from 7032700 to 14065400 to match the doubled workload. Additionally, the Wren source was cleaned up by removing forward declaration placeholders for global variables and converting them to proper `var` declarations with immediate initialization.

2015-08-27 13:25:24 +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

fix: double delta_blue benchmark iterations and update expected result

2015-08-27 13:25:24 +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

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.