wren/test at e0984a5012a2307bba60a6c51a53ae6da34c3547 - wren

Files

T

Bob Nystrom e0984a5012 fix: require parentheses for zero-argument join() method on Sequence

The zero-argument overload of `join` on `Sequence` was previously defined as a
getter-style method without parentheses. This change makes it a regular method
that requires explicit parentheses, consistent with the one-argument `join(sep)`
variant and standard Wren method syntax. The implementation now reads
`join() { join("") }` instead of `join { join("") }`.

All call sites in tests and documentation are updated accordingly.

2015-09-16 14:15:48 +00:00

api

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

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

benchmark

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

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

core

fix: require parentheses for zero-argument join() method on Sequence

2015-09-16 14:15:48 +00:00

language

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

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