Skip to content

spec: §2.9 and §2.5 state their backend status honestly (#537) - #538

Merged
gafferongames merged 1 commit into
mainfrom
spec-status-537
Sep 4, 2026
Merged

spec: §2.9 and §2.5 state their backend status honestly (#537)#538
gafferongames merged 1 commit into
mainfrom
spec-status-537

Conversation

@gafferongames

Copy link
Copy Markdown
Contributor

Closes #537. SPEC-TABLES.md §2.9 said the C++ reference and the tool carry unbounded arrays and named a tables/lists corpus; neither exists in the tree. It now reads owed, not emitted, on the terms §3.3 and §6.6 take, with the corpus named as what the implementation owes. §2.5's status line now says the *wstring blob is specified ahead of its implementation and not yet emitted. Docs only.

🤖 Generated with Claude Code

The unbounded array section claimed the reference and the tool carry it and
named a tables/lists corpus that does not exist. It now says owed, not emitted,
like every other section that landed ahead of its implementation, and names
the corpus as what the implementation owes. The byte-buffer section's status
line now says the *wstring blob is specified and not yet emitted.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@gafferongames
gafferongames merged commit 1711ee0 into main Sep 4, 2026
20 checks passed
@gafferongames
gafferongames deleted the spec-status-537 branch September 4, 2026 16:41
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.

SPEC-TABLES §2.9 claims a backend status the tree does not carry

2 participants