-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
btree: merge the implementations of MergeIter #78015
Conversation
☔ The latest upstream changes (presumably #78060) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:
|
5054f04
to
cc87f6e
Compare
@rustbot modify labels: +S-waiting-on-review -S-waiting-on-author |
@bors r+ rollup=never |
📌 Commit cc87f6ec3cc28a3c2b4c90631a3e9c6c92bad5d2 has been approved by |
🔒 Merge conflict This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again. How do I rebase?Assuming
You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial. Please avoid the "Resolve conflicts" button on GitHub. It uses Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Error message
|
cc87f6e
to
2c5f64f
Compare
@bors r+ rollup=never |
@ssomers: 🔑 Insufficient privileges: Not in reviewers |
@ssomers: 🔑 Insufficient privileges: not in try users |
@rustbot modify labels: +S-waiting-on-review -S-waiting-on-author |
@bors r+ rollup=never |
📌 Commit 2c5f64f has been approved by |
☀️ Test successful - checks-actions |
Also remove the gratuitous Copy bounds. Same benchmark performance.
r? @Mark-Simulacrum