wren/test at 6394e1c486fd5fcc108051f687f5df7c91e54784 - wren

Files

T

Bob Nystrom 6394e1c486 feat: add Stdin.readByte() method for reading single byte from stdin

Implement a new `readByte()` static method on the `Stdin` class that reads one byte from standard input, blocking the current fiber until a byte is received. The method returns the byte value as a number or `null` if stdin is closed.

Refactor the internal buffering mechanism by introducing a shared `read_()` helper method that both `readByte()` and `readLine()` use, replacing the previous per-method buffering logic. The `readByte()` implementation peels off the first byte from the internal `__buffered` string using `bytes[0]` and slicing.

Add two test files: `read_byte.wren` verifying byte-by-byte reading of "first" and "second" input lines, and `read_byte_eof.wren` confirming that reading after stdin is closed returns the expected error message.

2016-05-20 18:50:14 +00:00

api

fix: count subscript parameters in wrenMakeCallHandle for bracket signatures

2016-05-04 13:29:44 +00:00

benchmark

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

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

core

test: add test verifying closures of same code are unequal

2016-03-26 21:22:38 +00:00

feat: add Stdin.readByte() method for reading single byte from stdin

2016-05-20 18:50:14 +00:00

language

feat: report undefined variable errors on the line where they are used

2016-03-16 15:00:28 +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.