wren/test at 409873c38289778e9a0ae08c4d8a68fcd07727ab - wren

Files

T

Bob Nystrom 409873c382 perf: replace O(n) linear scan with O(1) map lookup for constant deduplication in compiler

Replace the linear scan of the function's constant table in `addConstant()` with a hash map lookup using a new `ObjMap* constants` field on the `Compiler` struct. This avoids O(n) performance degradation when compiling functions with many constants, such as large literal-heavy functions. The map stores constant values as keys and their index as numeric values, lazily initialized on first insertion. Also adds OBJ_FN hashing support in `hashObject()` to allow bare function objects as map keys internally, and includes a regression test with 65,550 constant entries to validate the fix.

2016-08-16 14:43:34 +00:00

api

refactor: rename list C API functions and remove Slot suffix for consistency

2016-07-28 15:06:36 +00:00

benchmark

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

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

core

feat: remove List.new(_) constructor and consolidate into List.filled(_,_)

2016-08-04 05:42:31 +00:00

feat: add Stdin.isTerminal method to detect TTY connection

2016-05-21 19:51:11 +00:00

language

feat: implement expression evaluation and statement detection in REPL with Meta.compileExpression

2016-05-21 06:03:05 +00:00

limit

perf: replace O(n) linear scan with O(1) map lookup for constant deduplication in compiler

2016-08-16 14:43:34 +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.