Don't treat negative trait predicates as always knowable#114080
Don't treat negative trait predicates as always knowable#114080bors merged 1 commit intorust-lang:masterfrom
Conversation
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (2efa46d): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
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: 652.287s -> 652.317s (0.00%) |
|
probably some weird inlining changes, but mostly positive so 🤷 or maybe it' not noise but slight changes in how we compute stuff, given that it only impacts incremental. Anyways, don't think there's anythign we should do here |
|
A small mixture of tiny wins and losses, nothing to worry about. @rustbot label: +perf-regression-triaged |
|
The outsized |
We don't need this. It was added in #90104 but I don't really know why. It's not sound afaict -- negative trait predicates need the same coherence-ambiguity/orphan check rules as positive ones.
r? @lcnr
cc @spastorino, do you remember why?