Implement feature integer_casts#157402
Conversation
|
rustbot has assigned @Mark-Simulacrum. Use Why was this reviewer chosen?The reviewer was selected based on:
|
This comment has been minimized.
This comment has been minimized.
|
Reminder, once the PR becomes ready for a review, use |
|
@rustbot ready |
|
That wording works for me. @bors r+ rollup |
Implement feature `integer_casts` Tracking issue: rust-lang#157388
Implement feature `integer_casts` Tracking issue: rust-lang#157388
This comment has been minimized.
This comment has been minimized.
|
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) |
This comment was marked as outdated.
This comment was marked as outdated.
|
⌛ Testing commit d79b87b with merge 47e54da... Workflow: https://github.com/rust-lang/rust/actions/runs/27116431268 |
Implement feature `integer_casts` Tracking issue: #157388
|
Tree is now open for merging. |
|
Auto build was cancelled. Cancelled workflows: The next pull request likely to be tested is #157402. |
|
⌛ Testing commit d79b87b with merge e6f8fdb... Workflow: https://github.com/rust-lang/rust/actions/runs/27116808211 |
Implement feature `integer_casts` Tracking issue: #157388
|
Auto build was cancelled. Cancelled workflows: The next pull request likely to be tested is #155607. |
…uwer Rollup of 9 pull requests Successful merges: - #157599 (`rust-analyzer` subtree update) - #157298 (Use alternate means of detecting enums in `is_udt`) - #155338 (Staticlib hide internal symbols) - #157402 (Implement feature `integer_casts`) - #157452 (Fix WASI links) - #157535 (Rename `errors.rs` file to `diagnostics.rs` (2/N)) - #157585 (Rename `errors.rs` file to `diagnostics.rs` (3/N)) - #157588 (Use `mul nuw nsw` in `intrinsics::copy`) - #157592 (Suggest comma multiple)
|
@rust-timer build d65ab4d |
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (d65ab4d): comparison URL. Overall result: ❌✅ regressions and improvements - please read:Benchmarking means the PR may be perf-sensitive. It's automatically marked not fit for rolling up. Overriding is possible but disadvised: it risks changing compiler perf. Next, please: If you can, justify the regressions found in this try perf run in writing along with @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 1.3%, secondary 3.6%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -2.8%)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: 516.268s -> 516.499s (0.04%) |
|
Caused the perf regression in #157600 |
|
I'm unsure how it could cause such a significant change in the first place, to be honest. |
|
@jhpratt @JonathanBrouwer I think it's fairly obvious. All the regressions are for creating docs. This PR adds ~288 trait implementations to the standard library that end up being documented/processed. If the trait ends up being perma-unstable I can see us |
|
Does adding trait impls to the stdlib also make downstream crates slower to document? I guess that makes sense to some degree but still interesting |
|
Yes, but also not by much. Adding 288 new impls is quite a lot and only resulted in 0.3-1% slowdowns, with 1.5% being an exception on It's not my decision but I don't think further action is required at this time. |
|
I agree, but I'll cc the rustdoc team so they at least know about it Cc @rust-lang/rustdoc |
View all comments
Tracking issue: #157388