-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Skip possible where_clause_object_safety lints when checking multiple_supertrait_upcastable
#106253
Conversation
☔ The latest upstream changes (presumably #106324) made this pull request unmergeable. Please resolve the merge conflicts. |
This needs a rebase just to add the lint back. I think the changes look fine, maybe |
@rustbot author |
cc @davidtwco, @compiler-errors, @JohnTitor, @estebank, @TaKO8Ki Some changes occurred to the core trait solver cc @rust-lang/initiative-trait-system-refactor Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
@rustbot ready |
Looks good to me! @bors r+ |
☀️ Test successful - checks-actions |
1 similar comment
☀️ Test successful - checks-actions |
Finished benchmarking commit (d117135): 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.
|
Fix #106247
To achieve this, I lifted the
WhereClauseReferencesSelf
out fromobject_safety_violations
and move it intois_object_safe
(which is changed to a new query).cc @dtolnay
r? @compiler-errors