Repository navigation
v2 tokenize: bind EmptyPattern on 01_tokenize's import chain (N7 resolve link) - #13501
Closed
gunbai-bot[bot] wants to merge 2 commits into
Closed
gunbai-bot[bot] wants to merge 2 commits into
gunbai-bot[bot] wants to merge 2 commits into
Conversation
…olve link) The nullary arm of lex_match_pattern resolved only through the deleted corpus-wide spelling search; the native resolver refuses it as unbound (advisory: declared in several modules). Bind it on the module's chain like target_model does. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Oct 7, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Oct 8, 2026
3 tasks
Contributor
Author
|
Superseded by #13641 (v1 closeout): this head is an ancestor of integration/v1-closeout. |
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.
N7 link: EmptyPattern unbound.
lex_match_patterninv2.compiler.tokenizematches the nullaryLexPatternarmEmptyPattern, but the module never imported it. The record-shaped arms (LiteralPattern { … }and the rest) are judged against the scrutinee type. A bare nullary name in pattern position, though, has to be bound by scope, or it would read as a binder. Since the corpus-wide spelling search was deleted from resolve, nothing binds it, and the native resolver refuses withresolve_reason_unbound_symbol(advisory:resolve_unbound_name_is_declared_in_several_modules).v2.std.compilers.target_modelalready imports it fromv2.std.compilers.lexing. This adds the same import to01_tokenize.§6b: the earliest unjustified link is the import list of the consuming module. The resolver's refusal is correct and stays as it is.
Target
//v2/test/parse/expression_bodied_fn_decl_parse:all38db1680-9612-4df4-8eff-0e7a6c512d59. EmptyPattern unbound appears in every member's cause chain (16 occurrences).1a68a746-6138-4649-808e-53d485d49708. EmptyPattern is gone from every chain (0 occurrences).Blocker EmptyPattern cleared. Next blocker:
countunbound (#13307), unchanged at the head of the chain. The fatal cause is stillprojection_receiver_declaration_unavailableuntil the rest of the chain clears.🤖 Generated with Claude Code