Skip to content

Rollup of 10 pull requests - #79377

Merged
bors merged 22 commits into
rust-lang:masterfrom
jonas-schievink:rollup-ye81i66
Nov 24, 2020
Merged

Rollup of 10 pull requests#79377
bors merged 22 commits into
rust-lang:masterfrom
jonas-schievink:rollup-ye81i66

Conversation

@jonas-schievink

Copy link
Copy Markdown
Contributor

Successful merges:

Failed merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

jyn514and others added 22 commits November 22, 2020 12:59
This gets rid of a bunch of `unwrap()`s and makes it a little more clear
what's going on.
Originally I wanted to make `fold_item` non-nullable too, which would
have been a lot nicer to work with, but unfortunately `stripper` does
actually return `None` in some places. I might make a follow-up moving
stripper to be special and not a pass so that passes can be
non-nullable.
This will allow linking to things like `Result<T, !>`.
Change `-Z fewer-names` into an optional boolean flag and allow using it
to either discard value names when true or retain them when false,
regardless of other settings.
This is useful for embedded targets where small code size is desired.
For example, on my project (thumbv7em-none-eabi) this yields a 0.6% code size reduction.
This section documents the exploit mitigations applicable to the Rust
compiler when building programs for the Linux operating system on the
AMD64 architecture and equivalent.
…veklabnik
Add exploit mitigations chapter to the rustc book
This section documents the exploit mitigations applicable to the Rust compiler when building programs for the Linux operating system on the AMD64 architecture and equivalent. This was done for a project I'm currently working on, and I hope it'll also be helpful to others.
Make `fold_item_recur` non-nullable
This gets rid of a bunch of `unwrap()`s and makes it a little more clear
what's going on.
Originally I wanted to make `fold_item` non-nullable too, which would
have been a lot nicer to work with, but unfortunately `stripper` does
actually return `None` in some places. I might make a follow-up moving
stripper to be special and not a pass so that passes can be
non-nullable.
Found while working on #76998.
Get rid of `doctree::Impl`
Follow-up to #79264, continues breaking up #78082. At some point I want to introduce `MaybeInlined`, but I think I'll wait until I need `MaybeInlined::InlinedWithOriginal` because it's not very useful in other situations.
r? ``@GuillaumeGomez``
Accept '!' in intra-doc links
This will allow linking to things like `Result<T, !>`.
*See <https://github.com/rust-lang/rust/pull/77832#discussion_r528409079>.*
r? ``@jyn514``
Allow using `-Z fewer-names=no` to retain value names
Change `-Z fewer-names` into an optional boolean flag and allow using it
to either discard value names when true or retain them when false,
regardless of other settings.
Fix typo in `keyword` docs for traits
This PR fixes a small typo in the `keyword_docs.rs` file, describing the differences between the 2015 and 2018 editions of traits.
…lacrum
BTreeMap: cut out the ceremony around BoxedNode
The opposite direction of #79093.
r? ``@Mark-Simulacrum``
…crum
BTreeMap/BTreeSet: make public doc more consistent
Tweaks #72876 and #73667 and propagate them to `BTreeSet`.
Allow disabling TrapUnreachable via -Ztrap-unreachable=no
Currently this is only possible by defining a custom target, which is quite unwieldy.
This is useful for embedded targets where small code size is desired. For example, on my project (thumbv7em-none-eabi) this yields a 0.6% code size reduction: 132892 bytes -> 132122 bytes (770 bytes down).
Add note to use nightly when using expr in const generics
As recommended by `@Icnr` in #73899 and in zulip, I've added a note saying that const expressions can be used in nightly.
```
error: generic parameters may not be used in const operations
--> $DIR/issue-61935.rs:10:23
|
6 | Self:FooImpl<{N==0}>
| ^ cannot perform const operation using `N`
|
= help: const parameters may only be used as standalone arguments, i.e. `N`
= note: use feature(const_generics) and feature(const_evaluatable_checked) to enable this
error: aborting due to previous error
```
I hope the note is well written :sweat_smile:
@rustbotrustbot added the rollup A PR which is a rollup label Nov 24, 2020
@jonas-schievink

Copy link
Copy Markdown
ContributorAuthor

@bors r+ rollup=never p=10

@rustbot modify labels: rollup

@bors

bors commented Nov 24, 2020

Copy link
Copy Markdown
Collaborator

📌 Commit f049b0b has been approved by jonas-schievink

@borsbors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Nov 24, 2020
@bors

bors commented Nov 24, 2020

Copy link
Copy Markdown
Collaborator

⌛ Testing commit f049b0b with merge 53d19b3...

@bors

bors commented Nov 24, 2020

Copy link
Copy Markdown
Collaborator

☀️ Test successful - checks-actions
Approved by: jonas-schievink
Pushing 53d19b3 to master...

@borsbors added the merged-by-bors This PR was explicitly merged by bors. label Nov 24, 2020
@bors
bors merged commit 53d19b3 into rust-lang:masterNov 24, 2020
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merged-by-borsThis PR was explicitly merged by bors.rollupA PR which is a rollupS-waiting-on-borsStatus: 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.

11 participants

@jonas-schievink@bors@rustbot@jyn514@camelid@tmiasko@Takashiidobe@ssomers@Dirbaio@rcvalle@mendess