wren/test at fd1d095588d3996dabcd24171112f501763d7d90 - wren

Meson/wren

Files

Chayim Refael Friedman 041f1bab8d Fix returning from constructors (#845 )

* Fix returning from constructors

 1. Do not allow returning with a value
 2. Return the instance, correctly, even when the user returned explicitly

* revise error message for consistency, revise implementation details a bit, fix extra args to finishBody

* clarify tests a bit

* document constructor return

Co-authored-by: ruby0x1 <ruby0x1@pm.me>

2021-04-07 22:53:05 -07:00

api

rename some test functions that clash with libc (#936 )

2021-03-07 16:38:29 -08:00

benchmark

Fix deprecated Python timing in benchmark & give more error info. (#844 )

2021-01-30 21:40:20 -08:00

core

Disallow non-Num arguments in Num for min(_), max(_), clamp(_,_), pow(_) and atan(_) (#859 )

2021-04-07 22:04:58 -07:00

language

Fix returning from constructors (#845 )

2021-04-07 22:53:05 -07:00

limit

test: Fix some tests so they fail on expected error, not on syntax error. (#779 )

2020-07-14 20:14:08 -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.