wren/test at 7d7be7361ec10c648588cd33b27f982ee0fb8877 - wren

Files

T

Bob Nystrom 7d7be7361e feat: add Sequence.each method to iterate over elements with a function

Add a new `each` method to the Sequence class in the Wren programming language,
allowing iteration over sequence elements by passing each element to a provided
function. This replaces the previous pattern of using `map` with `Fiber.yield`
in examples, providing a more direct and idiomatic way to perform side effects
per element. The implementation includes a core library method in `core.wren`,
a C source string in `wren_core.c`, documentation in the Sequence markdown file,
and three test cases covering normal iteration, empty sequences, and non-function
argument error handling.

2015-04-01 14:10:21 +00:00

benchmark

feat: store precomputed hash in ObjString and use it for equality and hashing

2015-03-18 14:09:03 +00:00

core

feat: add Sequence.each method to iterate over elements with a function

2015-04-01 14:10:21 +00:00

fix: return null from IO.read on EOF instead of empty string

2015-03-07 09:10:18 +00:00

language

fix: prevent local variables from being in scope during their own initializer

2015-04-01 14:05:40 +00:00

limit

refactor: move benchmark directory under test and update all references

2015-03-14 19:45:56 +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.