[rustdoc] Correctly handle output options with --show-coverage#159411
[rustdoc] Correctly handle output options with --show-coverage#159411GuillaumeGomez wants to merge 3 commits into
Conversation
|
|
This comment has been minimized.
This comment has been minimized.
|
I haven't looked at the implementation, but it seems a bit weird to me to have an flag called #158929 suggests updating the documentation instead. |
e124008 to
f9abe70
Compare
If you want to generate the output in a file, that seems kinda logical to not have output on stdout. |
This comment has been minimized.
This comment has been minimized.
100% agree, but the CLI option is called Is there a way to know if some users are currently relying on the current behavior? (since this is a breaking change) |
|
|
f9abe70 to
1010137
Compare
|
Yeah, |
|
It's a nightly only option, so breaking changes are fine. Although in this case, as long as you don't use |
|
Oh! I thought Though I still think renaming it to |
|
A follow-up and an issue about doing it would be good since we'll need an FCP. ;) |
|
Created #159691 for the rename. |
|
@bors r+ |
[rustdoc] Correctly handle output options with --show-coverage Fixes rust-lang#158929. The `-o` option was ignored with `--show-coverage`. This PR takes it into account and makes it closer to how these options are handled in the rest of rustdoc. Considering `calculate_doc_coverage` was never really a pass and that I needed `RenderOptions` (for the `-o` option), I moved it out of passes. r? @camelid
[rustdoc] Correctly handle output options with --show-coverage Fixes rust-lang#158929. The `-o` option was ignored with `--show-coverage`. This PR takes it into account and makes it closer to how these options are handled in the rest of rustdoc. Considering `calculate_doc_coverage` was never really a pass and that I needed `RenderOptions` (for the `-o` option), I moved it out of passes. r? @camelid
Rollup of 12 pull requests Successful merges: - #159582 (Sync from portable simd 2026 07 20) - #158890 (Fix splat v0 mangling) - #159411 ([rustdoc] Correctly handle output options with --show-coverage) - #159647 (Remove `early_exit` closures) - #159656 (define a `Simd` type in `minicore`) - #156474 (Add paths for linked associated items) - #159211 (Fix debuginfo argument when invoking LLBC linker) - #159527 (Bring runtime symbols statics on par with foreign functions) - #159625 (Refactor is_opsem_inhabited) - #159652 (Remove `cfg(not(no_global_oom_handling))` from the `Drop` impl of `UniqueArcUninit`) - #159657 (Remove the blanket `#![cfg_attr(test, allow(unused))]` from bootstrap ) - #159663 (Add layout cycle hang regression test)
|
|
This pull request was unapproved. This PR was contained in a rollup (#159693), which was unapproved. |
Fixes #158929.
The
-ooption was ignored with--show-coverage. This PR takes it into account and makes it closer to how these options are handled in the rest of rustdoc.Considering
calculate_doc_coveragewas never really a pass and that I neededRenderOptions(for the-ooption), I moved it out of passes.r? @camelid