WF check normalized assoc types when considering builtin object bound candidates#152923
WF check normalized assoc types when considering builtin object bound candidates#152923ShoyuVanilla wants to merge 1 commit intorust-lang:mainfrom
Conversation
|
Gonna try crater with the old solver changes first. |
This comment has been minimized.
This comment has been minimized.
WF check normalized assoc types when considerting builtin object boun…
This comment has been minimized.
This comment has been minimized.
|
@craterbot check |
|
🚨 Error: missing start toolchain 🆘 If you have any trouble with Crater please ask in t-infra on Zulip |
|
It seems crater doesn't wait for the try build to complete, unlike the timer 😅 |
This comment has been minimized.
This comment has been minimized.
|
@craterbot check |
|
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
|
Finished benchmarking commit (9ee38f2): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary -3.3%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 481.762s -> 482.964s (0.25%) |
|
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
|
🎉 Experiment
Footnotes
|
|
Maybe I'm normalizing and wf checking too much. Perhaps I should just check the existential project bound from the relevant trait id of the candidate |
cc #152489