-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Open
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-perma-unstableStatus: The feature will stay unstable indefinitely.Status: The feature will stay unstable indefinitely.T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.Relevant to the rustdoc team, which will review and decide on the PR/issue.
Description
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)
Metadata
Metadata
Assignees
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-perma-unstableStatus: The feature will stay unstable indefinitely.Status: The feature will stay unstable indefinitely.T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.Relevant to the rustdoc team, which will review and decide on the PR/issue.