wren/test at 899a4ec76ea6aa980f17e0c41781ff41dae2a290 - wren

Files

T

Bob Nystrom d04057bf75 feat: add trigonometric methods and Num.pi constant to core library

Add acos, asin, atan, atan2, tan methods to Num class and expose Num.pi constant with value π. Include corresponding C primitives in wren_core.c and test files for each new method.

2015-03-21 19:54:08 +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: add trigonometric methods and Num.pi constant to core library

2015-03-21 19:54:08 +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.