wren/test at 550fd13565836b5079d31e4076b0071257ef1411 - wren

Files

T

Bob Nystrom 1e842bbb2e feat: store precomputed hash in ObjString and use it for equality and hashing

Cache the FNV-1a hash code in the ObjString struct at creation time, replacing the
on-the-fly sampling hash in hashObject() and enabling constant-time string equality
checks. Refactor string allocation into allocateString() and hashString() helpers,
remove the old wrenNewUninitializedString() declaration, and add a CONST_STRING
macro. Disable the unimplemented subscript range operator with a runtime error and
skip the related UTF-8 tests. Add a string_equals benchmark to measure the speedup.

2015-03-18 14:09:03 +00:00

benchmark

feat: store precomputed hash in ObjString and use it for equality and hashing

2015-03-18 14:09:03 +00:00

core

feat: store precomputed hash in ObjString and use it for equality and hashing

2015-03-18 14:09:03 +00:00

fix: return null from IO.read on EOF instead of empty string

2015-03-07 09:10:18 +00:00

language

refactor: move benchmark directory under test and update all references

2015-03-14 19:45:56 +00:00

limit

refactor: move benchmark directory under test and update all references

2015-03-14 19:45:56 +00:00

README.md

refactor: move benchmark directory under test and update all references

2015-03-14 19:45:56 +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.
io/ - Tests for the built in IO library. In other words, methods on the IO class. If a bug is in wren_io.c, it should 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.