Skip possible where_clause_object_safety lints when checking multiple_supertrait_upcastable#106253
Skip possible where_clause_object_safety lints when checking multiple_supertrait_upcastable#106253bors merged 4 commits intorust-lang:masterfrom
multiple_supertrait_upcastable#106253Conversation
|
☔ 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
WhereClauseReferencesSelfout fromobject_safety_violationsand move it intois_object_safe(which is changed to a new query).cc @dtolnay
r? @compiler-errors