docs: reconcile functions roadmap - #92
Merged
Merged
Conversation
Replace obsolete implementation phases with the current higher-order functions sequence and correct stale function history and list-field behavior.
nerdalytics
marked this pull request as ready for review
July 24, 2026 18:17
nerdalytics
marked this pull request as draft
July 24, 2026 18:19
nerdalytics
marked this pull request as ready for review
July 24, 2026 18:20
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
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 changed
implementation status and TinyWhale 0.1 milestone.
Never, non-capturingfunction values, indirect lowering, and typed fuzzing.
checker rejection rather than the stale invalid-Wasm behavior.
Why
The roadmap still marked expression unification as pending, linked to a plan
that is no longer present, and described behavior that no longer matches the
compiler. Contributors need a source-grounded continuation point before the
SemIR call-argument refactor begins.
Impact
This is documentation-only. It establishes non-capturing first-class function
values as the next language milestone and identifies the prerequisites and
non-goals without changing compiler behavior.
Validation
None, and list-field behavior againstcompiler source and tests.
git diff --checksuccessfully.mise run cipipeline successfully.Build and Testpassed in run 30116369894.