docs: reconcile stale "#255 blocker" refs — loop-codegen defect is fixed#678
Merged
Merged
Conversation
Issue #255 (for-in/while loop bodies never execute in compiled wasm) was fixed in PR #257 (commit 85488d7, an ~8-line array-offset correction) and the issue was closed 2026-05-19. Verified on current main: freshly compiled loops execute their bodies (while->55, for->15, the #255 combo fixture->34). But several roadmap docs still advertised #255 as a live runtime blocker, falsely gating INT-08 (DOM reconciler #183), INT-11 (browser parity), and the DOM bindings row on a resolved bug. Reconciled 7 references across: - docs/ECOSYSTEM.adoc (satellite registry + INT-08/INT-11 rows) - docs/bindings-roadmap.adoc (DOM row #7) - docs/TECH-DEBT.adoc (INT-08 row) Reconciliation is honest: states #255 is fixed (PR #257, closed 2026-05-19) and marks the DOM/INT-08 end-to-end runtime as "to be re-verified" rather than asserting it runs (not driven end-to-end here). Docs-only. Verified (dune 3.24.0): dune build exit 0, doc-truthing intact, soundness ledger all-5-properties hold. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Issue #255 (
for-in/whileloop bodies never execute in compiled wasm) was fixed in PR #257 (commit85488d74, an ~8-line array-offset correction) and closed 2026-05-19. Verified on currentmain: freshly compiled loops execute their bodies (while→55,for→15, the exact #255 combo fixture→34).But several roadmap docs still advertised #255 as a live runtime blocker, falsely gating INT-08 (DOM reconciler #183), INT-11 (browser parity), and the DOM bindings row on a resolved bug.
Fix — 7 references reconciled (docs-only)
docs/ECOSYSTEM.adoc— satellite registry + INT-08/INT-11 rowsdocs/bindings-roadmap.adoc— DOM row ci: Bump github/codeql-action from 4.31.10 to 4.35.1 #7docs/TECH-DEBT.adoc— INT-08 rowHonest reconciliation: states #255 is fixed (PR #257, closed 2026-05-19) and marks the DOM/INT-08 end-to-end runtime as "to be re-verified" rather than asserting it runs (not driven end-to-end in this change).
Why it matters
A false "blocked" on the roadmap misdirects effort — it implies INT-08/INT-11/DOM need a codegen fix that already shipped. Removing it clarifies that the next step there is runtime re-verification, not a bug fix.
Verification (real toolchain — dune 3.24.0)
🤖 Generated with Claude Code