wren/test at c00d6ad6949119b810bd73afb01c6dcd2d6c5551 - wren

Files

T

Thorbjørn Lindeijer c00d6ad694 Added Sequence.each

This is a bit of a style preference since of course you can always write
the same thing with a for loop. However, I think sometimes the code
looks better when using this method.

It also provides an alternative to Sequence.map for cases where you
don't need the resulting list, and one that becomes especially necessary
when Sequence.map is changed to return a new sequence. The example in
the README.md file was using Sequence.map in a way that required this
alternative in that case.

2015-03-31 21:53:29 +02:00

benchmark

Store hash code in strings.

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

core

Added Sequence.each

2015-03-31 21:53:29 +02: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.