Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Rollup of 10 pull requests #47276

Merged
merged 23 commits into from
Jan 9, 2018
Merged

Rollup of 10 pull requests #47276

merged 23 commits into from
Jan 9, 2018

Conversation

zackmdavis and others added 16 commits January 6, 2018 11:17
This `horizontal_trim` function strips the leading whitespace from
doc-comments that have a left-asterisk-margin:

  /**
   * You know what I mean—
   *
   * comments like this!
   */

The index of the column of asterisks is `i`, and if trimming is deemed
possible, we slice each line from `i+1` to the end of the line. But if, in
particular, `i` was 0 _and_ there was an empty line (as in the example
given in the reporting issue), we ended up panicking trying to slice an
empty string from 0+1 (== 1).

Let's tighten our check to say that we can't trim when `i` is even the same
as the length of the line, not just when it's greater. (Any such cases
would panic trying to slice `line` from `line.len()+1`.)

Resolves rust-lang#47197.
The same effect can be achieved using -Cllvm-args=-debug

Refs rust-lang#46437 as it removes LLVMRustSetDebug()
Refs rust-lang#46437 as it also removes LLVMRustWriteDebugLocToString()
As a side effect, this fixes the warning about repr(C, simd) that has been reported during x86_64 windows builds since rust-lang#47111 (see also: rust-lang#47103)
It is also intended for use with unions.
…blems_in_computer_science, r=QuietMisdreavus

fix the doc-comment-decoration-trimming edge-case rustdoc ICE

This `horizontal_trim` function strips the leading whitespace from
doc-comments that have a left-asterisk-margin:

```
  /**
   * You know what I mean—
   *
   * comments like this!
   */
```

The index of the column of asterisks is `i`, and if trimming is deemed
possible, we slice each line from `i+1` to the end of the line. But if, in
particular, `i` was 0 _and_ there was an empty line (as in the example
given in the reporting issue), we ended up panicking trying to slice an
empty string from 0+1 (== 1).

Let's tighten our check to say that we can't trim when `i` is even the same
as the length of the line, not just when it's greater. (Any such cases
would panic trying to slice `line` from `line.len()+1`.)

Resolves rust-lang#47197.
Remove unused LLVM related code

Ticks a few more boxes on rust-lang#46437
@rust-highfive
Copy link
Collaborator

r? @nikomatsakis

(rust_highfive has picked a reviewer for you, use r? to override)

@kennytm
Copy link
Member Author

kennytm commented Jan 8, 2018

@bors r+ p=11

@bors
Copy link
Contributor

bors commented Jan 8, 2018

📌 Commit 97de5c1 has been approved by kennytm

@kennytm kennytm added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Jan 8, 2018
…richton

Replace empty array hack with repr(align)

As a side effect, this fixes the warning about repr(C, simd) that has been reported during x86_64 windows builds since rust-lang#47111 (see also: rust-lang#47103)

r? @alexcrichton
Rename ReprExtern to ReprC

… and similarily rename a few other field and locals that mentioned "extern repr".
rustc::ty: Rename struct_variant to non_enum_variant

r? @eddyb
…t, r=GuillaumeGomez

rustdoc: Don't import macros from private imports

Fixes rust-lang#47038
Don't look for niches inside generator types. Fixes rust-lang#47253

r? @eddyb
…etMisdreavus

Add missing links

r? @QuietMisdreavus

(please wait for CI, I have a few doubts about the `Write` trait links...)
@kennytm kennytm changed the title Rollup of 11 pull requests Rollup of 10 pull requests Jan 8, 2018
@kennytm
Copy link
Member Author

kennytm commented Jan 8, 2018

@bors r+

Removed #47248 — author changed code after r+.

@bors
Copy link
Contributor

bors commented Jan 8, 2018

📌 Commit 9ef9854 has been approved by kennytm

@bors
Copy link
Contributor

bors commented Jan 8, 2018

⌛ Testing commit 9ef9854 with merge 767b40396b16815dbe8a05d5be0b76f0835d6d00...

@bors
Copy link
Contributor

bors commented Jan 8, 2018

💔 Test failed - status-appveyor

@kennytm
Copy link
Member Author

kennytm commented Jan 9, 2018

@bors retry

bors added a commit that referenced this pull request Jan 9, 2018
Rollup of 10 pull requests

- Successful merges: #47210, #47233, #47246, #47254, #47256, #47258, #47259, #47263, #47270, #47272
- Failed merges: #47248
@bors
Copy link
Contributor

bors commented Jan 9, 2018

⌛ Testing commit 9ef9854 with merge 74966b5...

@bors
Copy link
Contributor

bors commented Jan 9, 2018

☀️ Test successful - status-appveyor, status-travis
Approved by: kennytm
Pushing 74966b5 to master...

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
rollup A PR which is a rollup S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.