Chris TateandClaude Opus 5.5 ee2832afae Answer undefined for out-of-range typed array reads like Node ...

Typed-array element reads at an index that is not an integer in
[0, length) now yield undefined instead of throwing a RangeError. The read
is `number | undefined`, like ordinary array reads; numeric and truthiness
consumers fuse back to the plain element read, which answers NaN for an
invalid index without touching storage. The may-throw seed for typed
reads is removed. Invalid writes stay ignored.

The corpus pins reads in printing, comparison, arithmetic, defaulting,
truthiness, bindings and templates, plus ignored writes, and a received
worker message is checked to arrive unfrozen.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-09 11:18:15 -05:00

..

src

Answer undefined for out-of-range typed array reads like Node

2026-10-09 11:18:15 -05:00

test

Answer undefined for out-of-range typed array reads like Node

2026-10-09 11:18:15 -05:00

vendor

Expand static support for common Effect 4 patterns (#600)

2026-10-01 17:36:29 -05:00

LICENSE

init

2026-07-22 18:08:04 -05:00

package.json

Release v0.2.7

2026-10-08 21:18:31 -05:00