wren/test at a3418dc06a34fa1aeb86b2f10d2a886219617dec - wren

Files

T

Bob Nystrom a3418dc06a feat: swap list insert arguments to index-first order and update all call sites

Swap the parameter order of `List.insert()` from `(item, index)` to `(index, item)`,
matching the convention used by most standard libraries. Update the C implementation
in `wren_core.c`, all documentation examples, and every test file to reflect the new
signature. Also restructure MSVC project files to match the new `src/cli/` and
`src/vm/` directory layout, add Visual Studio cache files to `.gitignore`, and fix
a trailing whitespace issue in `class_supertype`.

2015-03-17 14:01:09 +00:00

benchmark

refactor: move benchmark directory under test and update all references

2015-03-14 19:45:56 +00:00

core

feat: swap list insert arguments to index-first order and update all call sites

2015-03-17 14:01:09 +00:00

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

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

language

refactor: move benchmark directory under test and update all references

2015-03-14 19:45:56 +00:00

limit

refactor: move benchmark directory under test and update all references

2015-03-14 19:45:56 +00:00

README.md

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.