-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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.
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
Tracking Issue for rustdoc --test-builder
#102981
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
90 tasks
I don't think it was intended for being stabilized. |
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. |
--test-builder
?--test-builder
Relevent zulip discussion on rust-for-linux's use of this to enable running doctests in kernelspace. |
fmease
added a commit
to fmease/rust
that referenced
this issue
Nov 19, 2024
…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
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
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.
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?
--no-run
one.--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:
@GuillaumeGomez
The text was updated successfully, but these errors were encountered: