-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Avoid cloning the contents of a TokenStream
in a few places
#76696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
r? @eddyb (rust_highfive has picked a reviewer for you, use r? to override) |
@bors try @rust-timer queue |
Awaiting bors try build completion |
⌛ Trying commit 02c329a750a8c6ff6316fa53bec0f0fa6cf5005a with merge 1a4f4d775be4bc2c2f5522bc03b96be872f320cd... |
☀️ Try build successful - checks-actions, checks-azure |
Queued 1a4f4d775be4bc2c2f5522bc03b96be872f320cd with parent 0b65a3d, future comparison URL. |
Finished benchmarking try commit (1a4f4d775be4bc2c2f5522bc03b96be872f320cd): comparison url. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up. @bors rollup=never |
02c329a
to
d7bd3bb
Compare
@bors try @rust-timer queue |
Awaiting bors try build completion |
⌛ Trying commit d7bd3bb08a795315a1b7d04c95cccfabc6d6497e with merge b92b6836477f4895834288298fb12e158d4c8cdd... |
☀️ Try build successful - checks-actions, checks-azure |
Queued b92b6836477f4895834288298fb12e158d4c8cdd with parent 25c8c53, future comparison URL. |
Finished benchmarking try commit (b92b6836477f4895834288298fb12e158d4c8cdd): comparison url. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up. @bors rollup=never |
merge conflicts |
r=me after rebase. |
d7bd3bb
to
f6aec82
Compare
@bors r=petrochenkov |
📌 Commit f6aec82 has been approved by |
☀️ Test successful - checks-actions, checks-azure |
No description provided.