[WIP] [DO NOT MERGE] combine #66020 and #66821.#66838
[WIP] [DO NOT MERGE] combine #66020 and #66821.#66838eddyb wants to merge 2 commits intorust-lang:masterfrom
Conversation
|
@bors try @rust-timer queue |
|
Awaiting bors try build completion |
[WIP] [DO NOT MERGE] combine #66020 and #66821. That is, the two fixes for #65510, and only for perf testing purposes. The fact that they both work to a comparable extent, while touching different parts of the trait system, made me curious if there would be any gains from having both. r? @nikomatsakis
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
|
☀️ Try build successful - checks-azure |
|
Queued 685e48b with parent 2539b5f, future comparison URL. |
|
Finished benchmarking try commit 685e48b, comparison URL. |
|
That's measurably better than just either #66020 or #66821 alone, wow. The cc @rust-lang/compiler @rust-lang/wg-traits I'm nominating this for discussion, so that we can find a way to land at least some of these changes. |
|
discussed in last week's T-compiler meeting Main conclusion:
removing nomination |
|
The caching changes already landed, and I closed #66020 already, closing this too. |
That is, the two fixes for #65510, and only for perf testing purposes.
The fact that they both work to a comparable extent, while touching different parts of the trait system, made me curious if there would be any gains from having both.
r? @nikomatsakis