Repository navigation
docs: frontend decision - #50
Merged
Merged
Conversation
5 tasks done
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.
Summary
Documentation only: the last box of the roadmap, incremental parsing with Tree-sitter, is retired by decision rather than delivered.
docs/architecture.md§3.1 gets a dated decision note: the frontend is the standard-libraryastmodule behind thebuild_hirseam the section already requires, the architecture tests enforce that no layer above the frontend touches a parser object, and every later phase was delivered against that frontend. Tree-sitter would add a native dependency, a second adapter to keep identical to the first, and incremental parsing whose benefit the engine already gets from the per-module persistent cache (§11), an edit re-analysing that module and its importers only, with the whole suite running in about two seconds.astfrontend and point at the note; the seam stays, so a Tree-sitter adapter producing the same PyHIR remains possible if error recovery on broken files or sub-second editor feedback ever becomes a requirement.No code changes.
Closes #41