Tell the truth about the backend and adoption - #975
Merged
Merged
Conversation
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 this changes
The public status still said there was no code generation and linked a closed tracker, while Deed now has an interpreter, a WebAssembly backend, compiled run/test paths and component output.
This updates README, P10 and the backend introduction to describe the implemented toolchain. It also refreshes the roadmap's 2026-08-12 measurements: 12 releases, 26 downloads, and still 0 Deed-specific files outside the organization against a control of 8.
Why this way
The distinction is now explicit: the compiler/toolchain works, while adoption remains the open project gate. That prevents more compiler work from being mistaken for progress on Stage 1.
What it still does not do
It does not close the release/crates.io version mismatch or the Stage 1 benchmark work. Those are the next separate actions.
Checks
cargo nextest run -p deed-driver --test documentation(31 passed)no code generationand closed#228references removed from the status documentsAI assistance: GitHub Copilot implemented and verified this change.