1
0
forked from Mirror/wren
Files
wren/test
Bob Nystrom f23c82071a Don't allow calling the root fiber.
The VM used to not detect this case. It meant you could get into a
situation where another fiber's caller had completed. Then, when it
tried to resume that fiber, the VM would crash because there was nothing
to resume to.

This is part of thinking through all the cases around re-entrancy. Added
some notes for that too.
2018-07-21 10:02:29 -07:00
..
2018-07-21 10:02:29 -07:00
2015-12-23 17:29:53 -08:00
2018-07-21 10:02:29 -07:00
2016-05-21 12:51:11 -07:00
2016-12-29 17:52:38 +00:00
2016-02-14 22:21:50 -08:00
2015-09-15 07:46:09 -07:00
2015-09-15 07:46:09 -07:00
2015-09-15 07:46:09 -07:00

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.