Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tracking Issue for rustdoc --test-builder #102981

Open
ojeda opened this issue Oct 12, 2022 · 3 comments
Open

Tracking Issue for rustdoc --test-builder #102981

ojeda opened this issue Oct 12, 2022 · 3 comments
Labels
C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC S-tracking-perma-unstable Status: The feature will stay unstable indefinitely. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.

Comments

@ojeda
Copy link
Contributor

ojeda commented Oct 12, 2022

The flag was added in the second commit of #64328, but I couldn't find a tracking issue (like #87022 for --no-run).

Is it meant to be stabilized?

  • If yes: please feel free to reuse this as the tracking issue like in the --no-run one.
  • If not: we are currently using it (together with --no-run) in the kernel to extract the source code of the tests, i.e. to achieve something similar to --persist-doctests, but for source code; or like --scrape-examples, but for doctests. Would there be a better/stable way to do that?

In the PR above @Mark-Simulacrum mentions:

This is largely intended for "advanced" users at this point (I'm not sure if we'll ever stabilize it)

@GuillaumeGomez
@ojeda ojeda mentioned this issue Oct 12, 2022
Open
90 tasks
@GuillaumeGomez GuillaumeGomez added the T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. label Oct 12, 2022
@GuillaumeGomez
Copy link
Member

GuillaumeGomez commented Oct 12, 2022 •
edited
Loading

I don't think it was intended for being stabilized.

@Mark-Simulacrum
Copy link
Member

That PR tried to make it unstable (see the call to unstable in lib.rs), so we should track down the gap or PR that stabilized it.

@dtolnay dtolnay changed the title rustdoc: Tracking Issue for --test-builder? Tracking Issue for rustdoc --test-builder Jan 23, 2023
@dtolnay dtolnay added C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC S-tracking-perma-unstable Status: The feature will stay unstable indefinitely. labels Jan 23, 2023
@aDotInTheVoid
Copy link
Member

Relevent zulip discussion on rust-for-linux's use of this to enable running doctests in kernelspace.

@aDotInTheVoid aDotInTheVoid mentioned this issue Nov 18, 2024
Merged
fmease added a commit to fmease/rust that referenced this issue Nov 19, 2024
@fmease
Rollup merge of rust-lang#133191 - aDotInTheVoid:whoops-thats-not-sta…
27acd5e 
…ble-and-might-never-be, r=fmease

rustdoc book: Move `--test-builder(--wrapper)?` docs to unstable section.

Tracking issue: rust-lang#102981

These have always been unstable, but were documented in the stable section in rust-lang#114651
rust-timer added a commit to rust-lang-ci/rust that referenced this issue Nov 19, 2024
@rust-timer
Unrolled build for rust-lang#133191
Loading
Loading status checks…
d076a26 
Rollup merge of rust-lang#133191 - aDotInTheVoid:whoops-thats-not-stable-and-might-never-be, r=fmease

rustdoc book: Move `--test-builder(--wrapper)?` docs to unstable section.

Tracking issue: rust-lang#102981

These have always been unstable, but were documented in the stable section in rust-lang#114651
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC S-tracking-perma-unstable Status: The feature will stay unstable indefinitely. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@ojeda @dtolnay @GuillaumeGomez @Mark-Simulacrum @aDotInTheVoid