Point to the unstable segment of an import path instead of to the whole path#158075
Conversation
|
r? @chenyukang rustbot has assigned @chenyukang. Use Why was this reviewer chosen?The reviewer was selected based on:
|
…uwer Rollup of 8 pull requests Successful merges: - #158129 (ensure the new solver bootstraps on CI) - #158134 (Rename `lint-rust-version` to `hint-msrv`) - #157926 (Implement `#[diagnostic::on_unknown]` for modules.) - #158075 (Point to the unstable segment of an import path instead of to the whole path) - #158084 (`-Znext-solver` Emit error instead of ICE when combining {int, float} var with alias) - #158128 (std: use correct low surrogate range in Windows standard I/O code) - #158132 (std: correctly report file size on UWP) - #158138 (Remove redundant check for `#[loop_match]` and `#[const_continue]`)
Rollup merge of #158075 - oli-obk:confusing-stability, r=mejrs Point to the unstable segment of an import path instead of to the whole path Brought to you by me being confused why a stable item reported an instability error.
|
@rust-timer build 08affa9 |
|
Missing artifact for sha |
|
@rust-timer build 08affa9 |
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (08affa9): comparison URL. Overall result: ❌ regressions - 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 3.8%, secondary 5.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 2.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: 481.965s -> 481.084s (-0.18%) |
|
This caused the perf regression in #158145. Is there anything we can do about it? |
|
We can revert this PR? That said I'm curious why this is a regression. |
Brought to you by me being confused why a stable item reported an instability error.