wren/test at e0ac88c22abcf2ce53e7e7630f365eabb8ef4d01 - wren

mirror of https://github.com/wren-lang/wren.git synced 2026-01-11 14:18:42 +01:00

Files

Bob Nystrom e0ac88c22a Revamp wrenCall to work with slots.

Now, you call wrenEnsureSlots() and then wrenSetSlot___() to set up the
receiver and arguments before the call. Then wrenCall() is passed a
handle to the stub function that makes the call. After that, you can
get the result using wrenGetSlot___().

This is a little more verbose to use, but it's more flexible, simpler,
and much faster in the VM. The call benchmark is 185% of the previous
speed.

2015-12-29 07:58:47 -08:00

api

Revamp wrenCall to work with slots.

2015-12-29 07:58:47 -08:00

benchmark

Add a benchmark for wrenCall().

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

core

Don't allow fibers as map keys.

2015-12-15 10:42:21 -08:00

Get rid of fiber for finalizers.

2015-12-28 08:06:29 -08:00

language

Allow call and unary expressions as map keys.

2015-12-22 16:00:50 -08:00

limit

Simple string interpolation.

2015-11-11 07:55:48 -08: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.