wren/test at c9390c624bf02a207d4cf03fe127d0861f069c21 - wren

Files

T

Bob Nystrom 1973934fa2 feat: add Stat.isFile, Stat.isDirectory, File.exists, and Directory.exists methods

Add four new file system checking functions: Stat.isFile and Stat.isDirectory for querying entry type from a Stat object, and File.exists and Directory.exists static methods that return booleans by attempting to stat the path and checking the appropriate type. Also bump MAX_METHODS_PER_CLASS from 12 to 14 to accommodate the new Stat foreign methods, and clean up unused Scheduler imports in existing stat tests.

2016-02-21 20:23:33 +00:00

api

feat: add wrenGetSlotType API to query low-level type of object in a slot

2016-02-19 15:18:00 +00:00

benchmark

feat: add wrenGetValueDouble API and benchmark for wrenCall() performance

2015-12-24 01:29:53 +00:00

core

fix: remove fiber support as map keys and revert to value-only key validation

2015-12-15 18:42:21 +00:00

feat: add Stat.isFile, Stat.isDirectory, File.exists, and Directory.exists methods

2016-02-21 20:23:33 +00:00

language

feat: allow call and unary expressions as map keys in compiler

2015-12-23 00:00:50 +00:00

limit

fix: add overflow check for jump distance in patchJump and emit error on too much code

2016-02-19 14:57:38 +00: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.