-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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 7 pull requests #33833
Rollup of 7 pull requests #33833
Conversation
GuillaumeGomez
commented
May 24, 2016
- Successful merges: Improve the long explanation of E0207. #33692, Fix references links #33759, Update repr_simd #33779, Add new error code tests #33781, Fixed expand/collapse shortcut to not conflict with browser shortcuts #33797, Fixed link in Rust Book (no-stdlib) #33810, std: Use memalign, not posix_memalign, on Android #33832
- Failed merges:
There are Duplicate link references in the article and the format is incorrect.
Allows both `T` and `t`. It had been [Shift]+[+] before.
Realized browsers use [Ctrl]+[+=] for zoom, so using [Shift]+[+=] for collapse/expand was not necessarily a conflict. Also a bugfix.
Fix a broken link in the rust book.
The previous explanation does not seem to explain what it means for an implementation parameter to be used or unused. The new explanation lists the three ways specific ways by which an impl parameter becomes constrained (taken from RFC 447). This also adds a link to RFC 447. The explanation has two different examples. The first is adapted from RFC 447, and shows an instance of E0207 on a impl for a type. The second one is a trait impl example adapted from issue rust-lang#22834. Closes rust-lang#33650
r? @jroesch (rust_highfive has picked a reviewer for you, use r? to override) |
@bors: r+ p=1 |
📌 Commit a0fc9cc has been approved by |
⌛ Testing commit a0fc9cc with merge 338ddd7... |
💔 Test failed - auto-win-gnu-32-opt-rustbuild |
Improve the long explanation of E0207. The previous explanation does not seem to explain what it means for an implementation parameter to be used or unused. The new explanation lists the three ways specific ways by which an impl parameter becomes constrained (taken from RFC 447). This also adds a link to RFC 447. The explanation has two different examples. The first is adapted from RFC 447, and shows an instance of E0207 on a impl for a type. The second one is a trait impl example adapted from issue rust-lang#22834. Closes rust-lang#33650 cc rust-lang#32777 r? @GuillaumeGomez
Fix references links There are duplicate link references in the article and just remove one of them.
…abnik Update repr_simd r? @steveklabnik
…abnik Add new error code tests r? @steveklabnik
Changed toggle all sections key to `T` Allows both `T` and `t`. It had been [Shift]+[+] before. In response to rust-lang#33791. cc @Manishearth r? @GuillaumeGomez
Fixed link in Rust Book (no-stdlib) Closes rust-lang#33806
@bors: r+ p=1 |
📌 Commit 4613835 has been approved by |
⌛ Testing commit 4613835 with merge 49719a6... |
💔 Test failed - auto-win-msvc-64-opt |
@bors: retry |
💔 Test failed - auto-win-gnu-64-opt |
@bors: retry |