Shift component type depth limit to catch more cases - #2685
Merged
fitzgen merged 1 commit intoSep 29, 2026
Merged
Conversation
A few cases leaked through the previous check so it's now checked in a "more core" location to affect all locations that handle type depth and possibly increment it.
alexcrichton
force-pushed
the
handle-more-deep-types
branch
from
September 28, 2026 19:50
73a562c to
6cae5fe
Compare
fitzgen
approved these changes
Sep 29, 2026
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
2 participants
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.
A few cases leaked through the previous check so it's now checked in a "more core" location to affect all locations that handle type depth and possibly increment it.