-
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 11 pull requests #38834
Rollup of 11 pull requests #38834
Conversation
```rust let vr = v.iter().filter(|x| { x % 2 == 0 }); ``` will now yield the following compiler output: ```bash ERROR binary operation `%` cannot be applied to type `&&_` NOTE this is a reference of a reference to a type that `%` can be applied to, you need to dereference this variable once for this operation to work NOTE an implementation of `std::ops::Rem` might be missing for `&&_` ``` The first NOTE is new. Bug rust-lang#33877
We don't actually use trampoline_setup.c and all the `*tf3` business seems related to f80/f128 business. Specifically this'll fix some warnings showing up during builds on OSX.
Since 8285ab5, which was merged in with rust-lang#38061, the help for the --print option is missing the surrounding [ ] around the possible options. Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
Due to rust-lang#28728 loop {} is very risky and can lead to fun debugging experiences like in rust-lang#38136. Besides, aborting is probably better behavior than an infinite loop.
book: use abort() over loop {} for panic Due to rust-lang#28728 `loop {}` is very risky and can lead to fun debugging experiences such as rust-lang#38136. Besides, aborting is probably better behavior than an infinite loop. r? @steveklabnik
Clarify zero-value behavior of `ctlz`/`cttz` intrinsics. Fixes rust-lang#34381.
…aumeGomez Clarify behavior of `VecDeque::insert`. Fixes rust-lang#37046.
…nkov Test for appropriate span on second custom derive Adds test for and closes rust-lang#36935.
Detect double reference when applying binary op ``` rust let vr = v.iter().filter(|x| { x % 2 == 0 }); ``` will now yield the following compiler output: ``` bash ERROR binary operation `%` cannot be applied to type `&&_` NOTE this is a reference of a reference to a type that `%` can be applied to, you need to dereference this variable once for this operation to work NOTE an implementation of `std::ops::Rem` might be missing for `&&_` ``` The first NOTE is new. Fix rust-lang#33877 ---- Thanks to @estebank for providing the original PR rust-lang#34420 (of which this is a tweaked rebase).
…turon std: Remove unused objects from compiler-builtins We don't actually use trampoline_setup.c and all the `*tf3` business seems related to f80/f128 business. Specifically this'll fix some warnings showing up during builds on OSX.
Fix doc for `escape_debug`
Replace uses of `#[unsafe_destructor_blind_to_params]` with `#[may_dangle]` CC rust-lang#34761 r? @pnkfelix
fix help for the --print option Since 8285ab5, which was merged in with rust-lang#38061, the help for the --print option is missing the surrounding [ ] around the possible options. Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
…meGomez Add more docs for CoerceUnsized and Unsize here be dragons r? @ubsan @steveklabnik
@bors: r+ p=1 |
📌 Commit 6316e43 has been approved by |
r? @brson (rust_highfive has picked a reviewer for you, use r? to override) |
⌛ Testing commit 6316e43 with merge 00f0990... |
💔 Test failed - status-travis |
Hmm, it seems I screwed up my fix to #38617 ; I recognize that old use of I thought I had pushed the corrected version but obviously I did not. |
Aha: I did push a corrected commit: b8669df but bors interpreted my r+ here: #38617 (comment) as if it was referring to 98218b3 (again!) |
☔ The latest upstream changes (presumably #38138) made this pull request unmergeable. Please resolve the merge conflicts. |
ctlz
/cttz
intrinsics. #38310, Clarify behavior ofVecDeque::insert
. #38581, Test for appropriate span on second custom derive #38607, Detect double reference when applying binary op #38617, std: Remove unused objects from compiler-builtins #38623, Fix doc forescape_debug
#38629, Replace uses of#[unsafe_destructor_blind_to_params]
with#[may_dangle]
#38664, Doc fix #38799, fix help for the --print option #38815, Add more docs for CoerceUnsized and Unsize #38816