[ty] Co-locate retained definition usage state#26019
Merged
charliermarsh merged 3 commits intoJun 25, 2026
Merged
Conversation
Typing conformance resultsNo changes detected ✅Current numbersThe percentage of diagnostics emitted that were expected errors held steady at 94.47%. The percentage of expected errors that received a diagnostic held steady at 89.19%. The number of fully passing files held steady at 95/134. |
Memory usage reportSummary
Significant changesClick to expand detailed breakdownflake8
trio
sphinx
prefect
|
|
1e02913 to
7a60dc2
Compare
7a60dc2 to
74278e8
Compare
charliermarsh
added a commit
that referenced
this pull request
Jun 25, 2026
## Summary Stacked on #26019. We reserve `ScopedDefinitionId` zero for the implicit unbound or undeclared definition. The mutable use-def builder needs that sentinel while constructing its indexed flow state, but retaining an explicit `Undefined` entry in every frozen `UseDefMap` is unnecessary. This introduces a small retained-definition wrapper that omits the sentinel when freezing the map and synthesizes it for lookup and enumeration. Definition IDs and the builder representation remain unchanged. Coverage for an empty scope verifies that the implicit definition remains observable through both APIs.
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
We now encode whether each retained definition is used directly in
RetainedDefinitionState, instead of retaining a separate parallel boolean vector inUseDefMap.The mutable builder continues to keep
all_definitionsandused_bindingsseparate, then combines them only when freezing the immutable map. This keeps mutation straightforward while removing one allocation and one byte per definition from the retained representation. A compile-time size assertion guarantees that the combined enum remains the same size asDefinitionState.