-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Fix depth check in ProofTreeVisitor. #117878
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @lcnr (or someone else) soon. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
Some changes occurred to the core trait solver cc @rust-lang/initiative-trait-system-refactor |
This comment has been minimized.
This comment has been minimized.
…mbiguity of projections. Bless test with more specific notes on the ambiguity cause.
Some changes occurred to the core trait solver cc @rust-lang/initiative-trait-system-refactor |
thanks 👍 @bors r+ rollup |
☀️ Test successful - checks-actions |
Finished benchmarking commit (6b771f6): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 675.256s -> 674.719s (-0.08%) |
The hack to cutoff overflows and cycles in the new trait solver was incorrect. We want to inspect everything with depth [0..10].
This fix exposed a previously unseen bug, which caused the compiler to ICE when invoking
trait_ref
on a non-assoc type projection. I simply added the guard in theAmbiguityCausesVisitor
, and updated the expected output for theauto-trait-coherence
test which now includes the extra note:r? @lcnr