Skip to content

Rollup of 13 pull requests - #44164

Closed
arielb1 wants to merge 30 commits into
rust-lang:masterfrom
arielb1:rollup
Closed

Rollup of 13 pull requests#44164
arielb1 wants to merge 30 commits into
rust-lang:masterfrom
arielb1:rollup

Conversation

panicbitand others added 30 commits August 7, 2017 02:24
The motivation here is to allow rustfmt to recover from parse errors
after failing to parse macros.
distcheck complains that this file references projects not cotnained in the tarball
Make the ./x.py script fail when run with an invalid command, like:
./x.py nonsense
This helps in case of chaining multiple runs, eg.:
./x.py biuld && ./x.py test
The crate itself is internally referenced by serde_derive.
This, as rust-lang#43813, is due to the author of rust-lang#43728 (specifically,
3645b06) being a damnably contemptible fool. Before this entire
fiasco, we would return early from the unusedness late lints pass if
the type of the expression within the `hir::StmtSemi` was `!`, `()`,
or a boolean: these types would never get to the point of being marked
as unused results. That is, until the dunce who somehow (!?) came to
be trusted with the plum responsibility of implementing RFC
1940 (`#[must_use]` for functions) went and fouled everything up,
removing the early returns based on the (stupid) thought that there
would be no harm in it, since we would need to continue to check these
types being returned from must_use functions (which was true for the
booleans, at least). But there was harm—harm that any
quarter-way-competent programmer would have surely forseen! For after
the new functional-must-use checks, there was nothing to stop the
previously-returned-early types from falling through to be marked by
the unused-results lint!—a monumentally idiotic error that has cost
the project tens of precious developer- and reviewer-minutes dealing
with the fallout here and in rust-lang#43813.
If 3645b06 is representative of the standard of craftsmanship the
rising generation of software engineers holds themselves to, I weep
for the future of our technological civilization.
Resolvesrust-lang#44119.
in particular:
* show how to create an iterator that yields multiple socket addresses
* show more failing scenarios
No need to depend on librustc! All we need is libstd
Closesrust-lang#44140
This commit removes the `specialization_cache` field of `TyCtxt` by moving it to
a dedicated query, which it turned out was already quite easily structured to do
so!
…turon
libcore: Implement cloned() for Option<&mut T>
None
…, r=arielb1
Add reset_err_count() to errors::Handler
The motivation here is to allow rustfmt to recover from parse errors after failing to parse macros (cc rust-lang/rustfmt#1742).
r? @nrc
…avus
Don't highlight # which does not start an attribute in rustdoc
Currently when we highlight some macros for rustdoc (e.g. `quote!` from https://github.com/dtolnay/quote), we get really bad syntax highlighting, because we assume that every token between a `#` character and the next `]` in the source must be an attribute.
This patch improves that highlighting behavior to instead only highlight after finding the `[` token after the `#` token.
(NOTE: I've only run this patch against https://github.com/nrc/rustdoc-highlight so if it doesn't build on travis that's why - I don't have a recent rustc build on this laptop)
I'm guessing r? @steveklabnik
include Cargo.{toml,lock} in rust-src tarball
The lock file is interesting because e.g. xargo could use it to build libstd against the same dependencies that were used for the main build. More generally speaking, just documenting in this form which exact dependencies should be used IMHO makes lots of sense.
I added the Cargo.toml mostly because having the lock without the toml feels odd. Of course, the toml contains references to paths that don't actually exist in the rust-src tarball. Not sure if that is considered a problem.
…xamples, r=QuietMisdreavus
Rewrite `std::net::ToSocketAddrs` doc examples.
in particular:
* show how to create an iterator that yields multiple socket addresses
* show more failing scenarios
done this as preliminary work while investigating rust-lang#22569
note: i haven't run doc tests on my machine for this, so would be good to confirm CI passes before approving
… r=Mark-Simulacrum
bootstrap: remove unneeded extern crate
The crate itself is internally referenced by serde_derive.
…_results, r=eddyb
un-regress behavior of `unused_results` lint for booleans
Resolvesrust-lang#44119.
…matsakis
compiletest: Change Config comments to doc comments
I plan to make the same change in compiletest-rs, to have some documentation in [the docs](https://docs.rs/compiletest_rs/0.2.9/compiletest_rs/common/struct.Config.html).
…akis
Fail ./x.py on invalid command
Make the ./x.py script fail when run with an invalid command, like:
```
./x.py nonsense
```
This helps in case of chaining multiple runs, eg.:
```
./x.py biuld && ./x.py test
```
…etMisdreavus
Fix invalid linker position
Fixesrust-lang#44120.
Result isn't "optimal" though because there are spaces at the end of some lines.
…r=Mark-Simulacrum
rustbuild: Fix dependencies of build-manifest
No need to depend on librustc! All we need is libstd
Closesrust-lang#44140
…r=eddyb
rustc: Remove `specialization_cache` in favor of a query
This commit removes the `specialization_cache` field of `TyCtxt` by moving it to
a dedicated query, which it turned out was already quite easily structured to do
so!
cc rust-lang#44137
Use a byte literal ASCII 0 instead of its decimal value
@SimonSapin noticed this in dtolnay/itoa#8.
@rust-highfive

Copy link
Copy Markdown
Contributor

Some changes occurred in HTML/CSS.

cc @GuillaumeGomez

@rust-highfive

Copy link
Copy Markdown
Contributor

r? @sfackler

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

@arielb1

Copy link
Copy Markdown
ContributorAuthor

@bors r+ p=10

@bors

bors commented Aug 29, 2017

Copy link
Copy Markdown
Collaborator

📌 Commit a5e3484 has been approved by arielb1

@arielb1

Copy link
Copy Markdown
ContributorAuthor

@bors r-

@arielb1arielb1 closed this Aug 29, 2017
@CentrilCentril added the rollup A PR which is a rollup label Oct 24, 2019
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

rollupA PR which is a rollup

Projects

None yet

Development

Successfully merging this pull request may close these issues.

16 participants

@arielb1@rust-highfive@bors@Centril@sfackler@panicbit@mystor@topecongiro@RalfJung@vorner@ishitatsuyuki@zackmdavis@frewsxcv@GuillaumeGomez@alexcrichton@dtolnay