Propagate recursion depth in collect_predicates_for_types#111736
Closed
matthewjasper wants to merge 1 commit intorust-lang:masterfrom
Closed
Propagate recursion depth in collect_predicates_for_types#111736matthewjasper wants to merge 1 commit intorust-lang:masterfrom
matthewjasper wants to merge 1 commit intorust-lang:masterfrom
Conversation
Contributor
I think that generally, relying on Looked for a safer approach to correctly updating the depth here which resulted in #111754. I hope you don't mind me opening a separate PR here, I already made the change to test that it works so just dropping that change and suggesting it in a review didn't feel useful. |
Contributor
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.
This only changes the
Obligation::newcall that caused the linked issue, but there are some others in the trait solver that should be looked at later.Bug was introduced in #109119, so fix might be worth backporting.
cc #111729
r? @lcnr