Conversation
Member
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
f43d80c to
9cf0e8e
Compare
alexcrocha
approved these changes
Apr 20, 2026
9cf0e8e to
3c94917
Compare
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.

In
get_or_create_singleton_class, we were lazily creating singleton classes and enqueueing their ancestors for linearization. The problem is that we invoke this method for handling definitions too and that happens after the resolution loop finished, which means that the enqueue work was always ignored.There are a few ways to solve this:
get_or_create_singleton_classinside of the resolution loop enqueue work and all others eagerly linearizeI believe 1 is not a good option as we'll need to loop through everything again, including unresolved references. Option 2 seems like the most elegant of all, but it might be a considerably large refactor, so I went with option 3 for now.