-
Notifications
You must be signed in to change notification settings - Fork 13k
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 21 pull requests #33486
Closed
Closed
Rollup of 21 pull requests #33486
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
On my system, when the processor is already loaded, and I try to run the test suite, e.g. compile-fail/dep-graph-assoc-type-trans.rs fails because of undecodable JSON. Running the compiler manually, I can see that the dep graph thread panics (and puts non-JSON on stderr) while `send`ing on `swap_out`, presumably because the other end has already quit. I think that in this case, we can just gracefully exit the thread.
Also move the "Thread type" section down a bit, since it is not so important anymore. Fixes: rust-lang#33321
The changed line makes it look like `unsafe` is allowed, but the first statement of `parse_item_foreign_fn` is: `self.expect_keyword(keywords::Fn)?;` So we get the strange "expected one of `fn`, `pub`, `static`, or `unsafe`, found `unsafe`". Fixes: rust-lang#27361
Broke up long lines in E0506 Trimmed E0506 comment to be under max line width Added function example to E0506 Changed example of erroneous code wording on E0506
Removed unnecessary use of threads from E0504 Cleaned up line ending on E0504 Added more examples for E0504 Changed to erroneous code wording Switched Rc example to thread/Arc example Added comments describing why errors no longer occur
We will no longer use `ccache` in the makefiles for our local dependencies like miniz, but they're so small anyway it doesn't really matter. Closes rust-lang#33285
The definition of this value recently changed slightly. It no longer corresponds directly to the target triple. Also shuffled things around to make the order of cfg descriptions more logical and added text related them to the target triple. cc rust-lang#33403
Since these impls can be scattered around quite a bit, it is nice to be able to jump to the location where individual methods and trait impls are defined. Fixes: rust-lang#30416
This should be `have` instead of `has`.
Cleanup of E0389 Added type-d out version of type in E0389 description
…les, r=nikomatsakis Add `TAGS.rustc.emacs`/`TAGS.rustc.vi` make targets Add `TAGS.rustc.emacs`/`TAGS.rustc.vi` make targets, (re-)including rustc source.
…klabnik Add process types documentation Part of rust-lang#29370. r? @steveklabnik
…tsakis dep_graph: avoid panicking in thread when channel closed On my system, when the processor is already loaded, and I try to run the test suite, e.g. compile-fail/dep-graph-assoc-type-trans.rs fails because of undecodable JSON. Running the compiler manually, I can see that the dep graph thread panics (and puts non-JSON on stderr) while `send`ing on `swap_out`, presumably because the other end has already quit. I think that in this case, we can just gracefully exit the thread.
…nkfelix mk: Fix building with --enable-ccache We will no longer use `ccache` in the makefiles for our local dependencies like miniz, but they're so small anyway it doesn't really matter. Closes rust-lang#33285
…Gomez std::thread docs: spawn() does not return a Thread anymore Also move the "Thread type" section down a bit, since it is not so important anymore. Fixes: rust-lang#33321
parser: do not try to continue with `unsafe` on foreign fns The changed line makes it look like `unsafe` is allowed, but the first statement of `parse_item_foreign_fn` is: ``` self.expect_keyword(keywords::Fn)?; ``` So we get the strange "expected one of `fn`, `pub`, `static`, or `unsafe`, found `unsafe`". Fixes: rust-lang#27361
rustdoc: add "src" links to individual impls Since these impls can be scattered around quite a bit, it is nice to be able to jump to the location where individual methods and trait impls are defined. NOTE: this needs an update to the CSS, which I'd like to leave for whoever is the "rustdoc frontend champion". The new [src] links are currently too large and bold. Also, the interaction with the "since version X" annotations is not good. Fixes: rust-lang#30416
Add detailed error explanation for E0506 Part of rust-lang#32777
Add detailed error explanation for E0504 Part of rust-lang#32777
…Manishearth Replace copy-pasted variable name with relevant one
errors in the doc
Remove rust flags from doc block Fixes rust-lang#33405 r? @Manishearth
Add detailed error explanation for E0389 Part of rust-lang#32777
…bnik Add an example to Wrapping's documentation. Such an example would have helped me understand `Wrapping` quicker. r? @steveklabnik
[Doc] Default cpu is "generic" (and not "default") See [line 305](/~https://github.com/phil-opp/rust/blob/a22ca2872ef6782306012e6817dc4b8b778c43e9/src/librustc_back/target/mod.rs#L305).
doc: Update reference with better description of target_env The definition of this value recently changed slightly. It no longer corresponds directly to the target triple. Also shuffled things around to make the order of cfg descriptions more logical and added text related them to the target triple. cc rust-lang#33403
Fix some some duplicate words.
doc: make RFC references consistent Always add a space and end sentence with a full stop.
doc: trim some needless code
…eGomez Fix Typo in Barrier::wait documentation This should be `have` instead of `has`.
Indicate struct names are code-like in doc-comment.
(rust_highfive has picked a reviewer for you, use r? to override) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
TAGS.rustc.emacs
/TAGS.rustc.vi
make targets #33256, Add process types documentation #33283, dep_graph: avoid panicking in thread when channel closed #33313, mk: Fix building with --enable-ccache #33314, std::thread docs: spawn() does not return a Thread anymore #33326, parser: do not try to continue withunsafe
on foreign fns #33336, rustdoc: add "src" links to individual impls #33382, Add detailed error explanation for E0506 #33384, Add detailed error explanation for E0504 #33386, Replace copy-pasted variable name with relevant one #33402, errors in the doc #33409, Remove rust flags from doc block #33410, Add detailed error explanation for E0389 #33412, Add an example to Wrapping's documentation. #33428, [Doc] Default cpu is "generic" (and not "default") #33430, doc: Update reference with better description of target_env #33437, Fix some some duplicate words. #33438, doc: make RFC references consistent #33439, doc: trim some needless code #33442, Fix Typo in Barrier::wait documentation #33456, Indicate struct names are code-like in doc-comment. #33459