-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Rollup of 5 pull requests #52245
Rollup of 5 pull requests #52245
Conversation
It elaborates over why we have to slice the 4-size src to 2-size (same as dst).
Better docs for copy_from_slice & clone_from_slice I copy-pasted the text from clone_from_slice to copy_from_slice 😄 @steveklabnik feel free to suggest changes. edit: closes rust-lang#49769
Fix typo in error message E0277 Fix a typo we stumbled upon by accident :) r? @estebank
…g, r=oli-obk Improve lint handling in rustdoc r? @oli-obk
…meGomez Avoid unwrapping in PanicInfo doc example. Fixes rust-lang#51768.
Fix typo in E0433 docs
@bors: r+ p=5 |
📌 Commit 985c5a7 has been approved by |
Rollup of 5 pull requests Successful merges: - #51701 (Better docs for copy_from_slice & clone_from_slice) - #52231 (Fix typo in error message E0277) - #52233 (Improve lint handling in rustdoc) - #52238 (Avoid unwrapping in PanicInfo doc example.) - #52241 (Fix typo in E0433 docs) Failed merges: r? @ghost
☀️ Test successful - status-appveyor, status-travis |
@GuillaumeGomez Just curious, why is it better to rollup the pull requests and then merge them, instead of merging them individually? Either way, the commits will be merged, right? |
Because like this, we merge them all at once instead of having to wait 3+ hours for each. |
Huh, bors seems to be really slow... |
Successful merges:
Failed merges:
r? @ghost