Rollup of 4 pull requests#156088
Conversation
Previously when adding a suggestion for using `Cow::into_owned()` instead of `ToOwned::to_owned()`, the compiler would just convert the methods `Span` into a `String` and do checks on that `String`. This PR adds an extra guard to that suggestion by checking if the method is `sym::to_owned_method`.
Add extra symbol check for `.to_owned()` Follow up of rust-lang#154646 Previously when adding a suggestion for using `Cow::into_owned()` instead of `ToOwned::to_owned()`, the compiler would just convert the methods `Span` into a `String` and do checks on that `String`. This PR adds an extra guard to that suggestion by checking if the method is `sym::to_owned_method`. r? @davidtwco since you added the review to the previous PR
…ted-consts, r=Kivooeo Move tests associated consts r? @Kivooeo moved tests into associated-consts
…gxiangfei2009 Do not depend on typeck to borrow-check inline consts. Instead fetch the type from the inline-const's MIR, which comes from exactly the same typeck information.
…tes, r=JonathanBrouwer Move tests attributes I moved some attribute tests out of the issues folder into the attribute folder, please find time to review
|
@bors r+ rollup=never p=5 |
|
Deliberately excluded the 2 failed merges in #156078 |
This comment has been minimized.
This comment has been minimized.
|
📌 Perf builds for each rolled up PR:
previous master: 696d5929af In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
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 696d592 (parent) -> 3d5dfdc (this PR) Test differencesShow 50 test diffsStage 1
Stage 2
Additionally, 6 doctest diffs were found. These are ignored, as they are noisy. Job group index
Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 3d5dfdc29f0e3ba6e0d31d1cd39bf2beac4ce4b4 --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
A job failed! Check out the build log: (web) (plain enhanced) (plain) Click to see the possible cause of the failure (guessed by this bot)And then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance non-200 OK status code: 504 Gateway Timeout body: "{"message": "We couldn't respond to your request in time. Sorry about that. Please try resubmitting your request and contact us if the problem persists."}\r\n" |
|
Finished benchmarking commit (3d5dfdc): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis perf run didn't have relevant results for this metric. Max RSS (memory usage)Results (primary -3.5%, secondary 1.3%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -3.0%, secondary -0.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 482.368s -> 481.836s (-0.11%) |
Successful merges:
.to_owned()#156074 (Add extra symbol check for.to_owned())r? @ghost
Create a similar rollup