Rustdoc nocapture

[GuillaumeGomez]

Following rust-lang/rust#86230.

It might need to wait for rustdoc latest nightly to be published first to pass CI though (so tomorrow).

Also: the --nocapture option is unstable for now in rustdoc, is there something particular to be done until it's stable on cargo side? For now I simply add -Zunstable-options but not sure if it's the way to go?

[rust-highfive]

r? @Eh2406

(rust-highfive has picked a reviewer for you, use r? to override)

[bors]

☔ The latest upstream changes (presumably #10408) made this pull request unmergeable. Please resolve the merge conflicts.

[ehuss]

Closing as this is a bit stale. I'm also not clear what this was needed, since it looks like one can just pass -Zunstable-options themselves. Before reopening, please work with the Cargo team to settle on a design for whatever is needed here.

[MingweiSamuel]

The current cargo doesn't work, I assume because --nocapture gets prefixed with --test-args. Right now cargo test -- --nocapture still hides input from doctests because it doesn't forward the --nocapture argument properly. This fixes that. See the referenced issues.

[veryjos]

Is this fixed?

[ptrself]

Doesn't seem like.. but in the interim, try this:

RUSTDOCFLAGS="-Z unstable-options --nocapture" cargo +nightly test --doc

[metasim]

@ehuss @GuillaumeGomez Can you please consider reopening this? It seems the hard work has already been done in rustdoc, and but given most people use rustdoc via cargo, it's availability is quite hindered. Or am I misinterpreting the state of --nocapture in rustdoc?

[GuillaumeGomez]

I can't reopen it so I'll let it up to cargo team.