mirror of
https://github.com/wren-lang/wren.git
synced 2026-01-11 22:28:45 +01:00
58e4d26648
Get rid of the separate opt-in IO class and replace it with a core System class. - Remove wren_io.c, wren_io.h, and io.wren. - Remove the flags that disable it. - Remove the overloads for print() with different arity. (It was an experiment, but I don't think it's that useful.) - Remove IO.read(). That will reappear using libuv in the CLI at some point. - Remove IO.time. Doesn't seem to have been used. - Update all of the tests, docs, etc. I'm sorry for all the breakage this causes, but I think "System" is a better name for this class (it makes it natural to add things like "System.gc()") and frees up "IO" for referring to the CLI's IO module.
18 lines
917 B
Markdown
18 lines
917 B
Markdown
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. |