-
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
Rollup of 16 pull requests #59885
Rollup of 16 pull requests #59885
Conversation
…n in the rustc book.
We relax the assumption that the discriminant is always field 0, in preparations for layouts like generators where this is not going to be the case.
This adds some extra docs for the `no-prefer-dynamic` header. And also a `s/must_compile_successfully/compile_pass`. `must_compile_successfully` has been renamed to `compile_pass` at some point in the past and this comment was still referring to the old name.
…ble compiler flags, instead of flags for debugging.
Fix lifetime on LocalInternedString::get function cc @eddyb @nnethercote
…petrochenkov Properly parse '--extern-private' with name and path It turns out that rust-lang#57586 didn't properly parse `--extern-private name=path`. This PR properly implements the `--extern-private` option. I've added a new `extern-private` option to `compiletest`, which causes an `--extern-private` option to be passed to the compiler with the proper path. Part of rust-lang#44663
Move back::link and debuginfo::type_names to cg ssa r? @eddyb
…rch, r=QuietMisdreavus Ensure that exact matches come first in rustdoc search Fixes rust-lang#59287. cc @scottmcm r? @QuietMisdreavus
Add discr_index to multi-variant layouts We remove the assumption that the discriminant is always field 0, in preparations for layouts like generators where this is not (always) going to be the case. Specifically, upvars are going to go before the discriminant. In theory, it's possible to remove _that_ assumption instead and keep the discriminant at field index 0, but one assumption or the other had to go :) There is one place I know of in the debuginfo code where we'll still need to remove assumptions that the discriminant is the _only_ field. I was planning on doing this along with the upcoming generator change, which will also include tests that exercise the code changing in this PR. r? @eddyb cc @oli-obk cc @cramertj
Use a proc macro to declare preallocated symbols r? @petrochenkov
…mertj Document the -Z flag to the rustc book # Description Changes: - Added new documentation on the `-Z` flag of rustc in the command-line arguments section of the rustc book. If I need to rephrase anything or if you have any improvements, please let me know! I deliberately did not create an exhaustive list of all options since they are likely to change over time and per toolchain version. closes rust-lang#41142
…-mut, r=pnkfelix Mark variables captured by reference as mutable correctly Closes rust-lang#59620 r? @pnkfelix
…ietMisdreavus Add back the substring test Fixes rust-lang#58331. r? @QuietMisdreavus
Final (one can only hope) futures_api adjustments Based on rust-lang#59119 -- this change is only the latter two commits. cc rust-lang#59725 r? @withoutboats
compiletest: Improve no_prefer_dynamic docs This adds some extra docs for the `no-prefer-dynamic` header. And also a `s/must_compile_successfully/compile_pass`. `must_compile_successfully` has been renamed to `compile_pass` at some point in the past and this comment was still referring to the old name.
Kill dead code dominator code. Hi, Whilst fiddling around in the dominator code, I found some (I think) unused code. This code *was* used at the time it was imported, but over time it seems to have become redundant. I've tested a build up to stage 1 with no problems. Maybe the tests will turn up something though. P.S. There is a FIXME comment in `dominators/mod.rs`: ``` pub fn is_dominated_by(&self, node: Node, dom: Node) -> bool { // FIXME -- could be optimized by using post-order-rank self.dominators(node).any(|n| n == dom) } ``` I'm not sure of the intention of this comment. The `Dominators` struct already operates over post-order rank nodes. Any ideas?
…idtwco improve unknown enum variant errors Fixes rust-lang#56517.
Remove strange formatting in `Ordering` docs. I can't really fathom what the intent of the brackets is. The [original PR](rust-lang#12956) doesn't give any hints. I think it seems fine without them.
std::ops::Div examples: correct nominator to numerator
SGX target: fix cfg(test) build
@bors r+ p=16 |
📌 Commit 3215b70 has been approved by |
⌛ Testing commit 3215b70 with merge 17ee368b48fdb40365792bffc3adf1d3e7e2587e... |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
💔 Test failed - checks-travis |
Successful merges:
Ordering
docs. #59831 (Remove strange formatting inOrdering
docs.)Failed merges:
r? @ghost