Skip to content

test(WO80/A4): rulings batch 4 — funcall, item algebra, boundary, tests - #822

Merged
ronaldtse merged 1 commit into
mainfrom
feat/a4-rulings-batch4
Oct 22, 2026
Merged

ronaldtse merged 1 commit into
mainfrom
feat/a4-rulings-batch4

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

Eight new normative vectors completing the A4 inventory's empirical sweep (points 4, 5, 7, 9, 10 — joining batches 1–3's points 1, 2, 3, 6 + the run-dispatch ruling).

Every vector was probed against the interpreter before being pinned — including two genuine findings: run accepts no kwargs (parse error), and stray identifiers are silently consumed at parse time (run nosuchfunction yields an empty stage — a typo'd map is silently wrong). The hazard is pinned as a ruling with a commented follow-up rather than a behavior change: the stricter parse is gated on a clean parse of the full corpus across all three compilers, which is exactly the IS-1 v2 opening item.

…edded tests

Empirically pinned against the interpreter, normative as IS-1 v2
sections:

- run <stdlib-name> dispatches Stdlib::Functions; run takes NO kwargs
  (kwargs belong to declared funcall directives — rababa); parse error
  otherwise
- stage-level case directives execute at their rule position on the
  whole string (downcase-then-sub ordering pinned)
- item algebra: any(<chars>) set, any(lo..hi) inclusive range,
  capture+ref source substitution
- boundary is a zero-width word edge (string edges match, mid-word
  never)
- embedded tests are normative data — never executed by transliterate;
  the verification layer runs them
- HAZARD pinned: stray identifiers (incl. unknown run targets) are
  consumed as parse no-ops — a typo'd map is silently wrong. Ruled
  tolerable for the legacy corpus; stricter parsing is an IS-1 v2
  follow-up gated on a clean 293-map parse across all three compilers
@ronaldtse
ronaldtse merged commit 6d76422 into main Oct 22, 2026
11 checks passed
@ronaldtse
ronaldtse deleted the feat/a4-rulings-batch4 branch October 22, 2026 08:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant