wren/test at load-module-result - wren - Gitea: Git with a cup of tea

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

Files

underscorediscovery 6d3739af65 Introduce WrenLoadModuleResult, fix unfreed strings from host.

The original attempt at handling the returns from loadModuleFn wasn't ideal. 889cae5ff1

Instead of making the host go via the VM allocation and need to understand it semantically, we can instead solve the problem of the unfreed return result directly.

This also opens up the option of providing a length parameter or other information needed later (length is optional, and not used as of right now, but exists to show intent).

2020-07-11 11:59:24 -07:00

api

Introduce WrenLoadModuleResult, fix unfreed strings from host.

2020-07-11 11:59:24 -07:00

benchmark

Fix horrendously bad bit hashing function.

2019-07-27 13:34:07 -07:00

core

core; num; add exp & log2

2020-07-10 19:38:45 -07:00

language

Support positive sign in scientific notation (#706 )

2020-06-13 21:37:30 -07: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.