Combine two loops in check_match#80367
Conversation
|
r? @varkor (rust-highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
|
Is there a way to combine these two loops after all given the borrowck error? |
|
r? @Nadrieril |
|
@camelid I think you can fix the error by removing |
5c65386 to
b68d851
Compare
|
Starting with a rebase. |
This comment has been minimized.
This comment has been minimized.
Ok, I tried that, but I ran into a lot of errors because |
Suggested by Nadrieril in rust-lang#79051 (comment).
b68d851 to
c3a03ae
Compare
|
I'll run perf on this after CI passes. |
|
@bors try @rust-timer queue |
|
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
|
bors seems to have lost track of this PR. Closing and reopening. |
|
@bors try @rust-timer queue |
|
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
|
⌛ Trying commit c3a03ae with merge cc556f91642435dd5ba31f27af2d573b5f9e1526... |
|
☀️ Try build successful - checks-actions |
|
Queued cc556f91642435dd5ba31f27af2d573b5f9e1526 with parent 0443424, future comparison URL. |
|
Finished benchmarking try commit (cc556f91642435dd5ba31f27af2d573b5f9e1526): comparison url. Summary: This benchmark run did not return any significant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. @bors rollup=never |
Ah yeah that's the change I hoped you could get, I was surprised you got borrow errors. LGTM and no perf impact, thanks! 💯 @bors r+ |
|
📌 Commit c3a03ae has been approved by |
|
☀️ Test successful - checks-actions |
Suggested by Nadrieril in
#79051 (comment).
Opening to get a perf run. Hopefully this code doesn't require everything in the
first loop to be done before running the second! (It shouldn't though.)
cc @Nadrieril