wren/test at 72c38a59cebbd924af4e5d4823e12f47be5e76ea - wren

Meson/wren

Files

Bob Nystrom 72c38a59ce More stuff for working with strings and bytes!

- "\x" escape sequence to put byte values in strings: "\x34"
- String.byteAt(index) gets value of byte in string.
- String.bytes returns a raw sequence of bytes for a string.
- String.codePointAt(index) gets the code point at an offset as a raw number.

2015-03-27 20:44:07 -07:00

benchmark

Store hash code in strings.

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

core

More stuff for working with strings and bytes!

2015-03-27 20:44:07 -07:00

Change IO.read to return null on EOF

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

language

More stuff for working with strings and bytes!

2015-03-27 20:44:07 -07:00

limit

Reorganize tests and benchmark scripts.

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