wren/test at 8ed0cde91caa2c896303fa8c9daa94c3ebc86198 - wren

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

Files

Bob Nystrom 8ed0cde91c Allow "var" in a class body for defining "properties".

A property is a field with an implicit getter, setter, and optional
class body initializer.

It's handy for defining publicly visible state in a class. When modules
are classes, this is needed for "top level" variables.

Right now, a class var gets both a getter and setter. It would be nice
to also have something like "val" for properties that are publicly
visible but not settable.

Also, still need to support "static var" for metaclass properties.

2015-12-21 08:04:39 -08:00

api

Clean up definition syntax:

2015-12-18 06:59:49 -08:00

benchmark

Allow "var" in a class body for defining "properties".

2015-12-21 08:04:39 -08:00

core

Clean up definition syntax:

2015-12-18 06:59:49 -08:00

Simple string interpolation.

2015-11-11 07:55:48 -08:00

language

Allow "var" in a class body for defining "properties".

2015-12-21 08:04:39 -08:00

limit

Clean up definition syntax:

2015-12-18 06:59:49 -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.