wren/test at 1661f5368f9f1aa475bf59bf8dc727893250191f - wren

mirror of https://github.com/wren-lang/wren.git synced 2026-01-11 22:28:45 +01:00

Files

Bob Nystrom 1661f5368f Allow passing a value when first starting a fiber.

If the function the fiber is created from takes a parameter, the value
passed to the first call() or transfer() gets bound to that parameter.

Also, this now correctly handles fibers with functions that take
parameters. It used to leave the stack in a busted state. Now, it's a
runtime error to create a fiber with a function that takes any more
than one parameter.

2017-10-19 20:45:13 -07:00

api

Add test for user data.

2017-03-22 07:26:19 -07:00

benchmark

Add a benchmark for wrenCall().

2015-12-23 17:29:53 -08:00

core

Allow passing a value when first starting a fiber.

2017-10-19 20:45:13 -07:00

Add Stdin.isTerminal.

2016-05-21 12:51:11 -07:00

language

Use strtoll() for hex literals to handle 64-bit ones even on 32-bit.

2017-01-12 21:53:21 -08:00

limit

Use a map to check for constant collisions.

2016-08-16 07:43:34 -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.
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.