wren/test at 92c2b2d5e0cbd0396fb7edf0d077f60115e625a3 - wren

Files

T

Bob Nystrom fe143644b3 Rationalize string lengths.

The .count getter on string returns the number of code points. That's
O(n), but it's consistent with the rest of the main string API.

If you want the number of bytes, it's "string".bytes.count.

Updated the docs.

Fixes 68. Woo!

2015-09-11 21:33:26 -07:00

api

No more default constructors.

2015-09-01 08:16:04 -07:00

benchmark

Merge branch 'master' into libuv

2015-08-28 23:13:56 -07:00

core

Rationalize string lengths.

2015-09-11 21:33:26 -07:00

No more default constructors.

2015-09-01 08:16:04 -07:00

language

Flesh out string byte handling a bit:

2015-09-10 23:52:18 -07:00

limit

Use "construct" instead of "this" to define constructors.

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