-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Rollup of 7 pull requests #139881
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 7 pull requests #139881
Conversation
These were low value even before rust-lang#137978 resulted in empty names being used much less. (Why check for non-emptiness in these three places? There are thousands of places in the compiler you could check.)
Field names are never empty, so the unwrap is unnecessary.
This is pretty weird code. As the `HACK` comment indicates, we push the empty ident here only to make the path longer, so certain checks to occur within `lint_if_path_starts_with_module`. `dummy` is a better choice because it explicitly communicates that the actual value doesn't matter.
The methods `Take::get_mut` and `Chain::get_mut` include comments warning about modifying the I/O state of the underlying reader. However, many readers (e.g. `File`) allow I/O using a shared reference (e.g. `&File`). So, add the same caveat to the `get_ref` methods.
…play, r=GuillaumeGomez `librustdoc`: more `impl fmt::Display` Continuation of rust-lang#137425 and rust-lang#136828 and rust-lang#136784 Working towards getting rid of the `write_str` helper r? `@GuillaumeGomez` (if you want!)
…=oli-obk Normalize ADT field in `find_tails_for_unsizing` See the comment inline and in the test. TL;DR is that we're getting getting a type from a `type_of` query and then matching on it structurally in codegen, so we're obligated to normalize it. The fact that this wasn't triggered earlier is that all of the types that have `CoerceUnsized` implementations never encounter aliases when peeling the ADT down to their base reference/ptr type. **NOTE**: I also renamed some things and reorganized the function a bit. Fixes rust-lang#139812 Fixes rust-lang#74451, which I didn't think was interesting enough to add another test. r? oli-obk
Use `rust-cache` to speed-up `citool` compilation Alternative to rust-lang#139678. r? ``@marcoieni``
…chenkov Remove safe remove `safe_remove_dir_all` and `safe_remove_file` use `canonicalize` to workaround a `MAX_PATH` limitation. However, this has not been needed in a long time, since the standard library handles this situation itself. I've kept `safe_remove_file` (without `canonicalize`) because it also returns `Ok` if the file is not found. While, `safe_remove_file` is only used twice, matching on the error kind is sufficiently verbose that maybe it's still worth it?
…-errors Reduce kw::Empty usage, part 5 Another step towards rust-lang#137978. r? `@davidtwco`
…obzol CI: rename MacOS runner r? ``@Kobzol``
Add warning comment to `Take::get_ref` and `Chain::get_ref` The methods `Take::get_mut` and `Chain::get_mut` include comments warning about modifying the I/O state of the underlying reader. However, many readers (e.g. `File`) allow I/O using a shared reference (e.g. `&File`). So, add the same caveat to the `get_ref` methods.
@bors r+ rollup=never p=5 |
☀️ Test successful - checks-actions |
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing 414da5b (parent) -> 38c560a (this PR) Test differencesShow 40 test diffsStage 1
Stage 2
Additionally, 36 doctest diffs were found. These are ignored, as they are noisy. Job group index
Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
📌 Perf builds for each rolled up PR:
previous master: 414da5b63d In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (38c560a): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results (primary -0.3%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResults (primary 0.5%, secondary 2.4%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 782.201s -> 781.698s (-0.06%) |
Successful merges:
librustdoc
: moreimpl fmt::Display
#138455 (librustdoc
: moreimpl fmt::Display
)find_tails_for_unsizing
#139818 (Normalize ADT field infind_tails_for_unsizing
)rust-cache
to speed-upcitool
compilation #139819 (Userust-cache
to speed-upcitool
compilation)Take::get_ref
andChain::get_ref
#139877 (Add warning comment toTake::get_ref
andChain::get_ref
)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup