Fix flaky recursion in recursive forward-reference resolution#4754
Merged
Conversation
Liam-DeVoe
approved these changes
May 28, 2026
c202e5d to
66cf41c
Compare
Resolving recursive forward references such as A = list[Union["A", str]] recursed once per available stack frame until hitting a RecursionError, then fell back to a deferred strategy. Termination therefore depended on the ambient stack depth, which made resolution flaky (spurious RecursionError and other intermittent failures). Break the cycle eagerly by deferring when we re-enter resolution of a type whose forward reference we are already resolving, so resolution uses a small and constant amount of stack. https://claude.ai/code/session_01F7S7ua4joqKCzxbMxQWj5R
66cf41c to
f3cbde1
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.
Resolving recursive forward references such as
A = list[Union["A", str]]recursed once per available stack frame until hitting a RecursionError, then fell back to a deferred strategy. Termination therefore depended on the ambient stack depth, which made resolution flaky (spurious RecursionError and other intermittent failures). Break the cycle eagerly by deferring when we re-enter resolution of a type whose forward reference we are already resolving, so resolution uses a small and constant amount of stack.