-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
[rustdoc] stabilize cfg(doctest) #63201
Conversation
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
e823147
to
ca0d1d0
Compare
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
ca0d1d0
to
7dcf3f0
Compare
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
7dcf3f0
to
07ab24b
Compare
Ping @rust-lang/rustdoc Btw, like said multiple times, a few (very big) crates depend on this feature because it's replacing |
See #62210 (comment): AFAIK no decision was made yet by the relevant team(s) (whichever ones that would be) which approach is the right one. The revert happened because just adding |
I think the implementation here looks good. However, I agree that the discussion @RalfJung notes should happen prior to landing stabilization. |
The original |
Fixes #62210.
Since we removed rustdoc from providing
cfg(test)
on test runs, it's been replaced bycfg(doctest)
. It'd be nice to have it in not too far in the future. :)cc @rust-lang/rustdoc
r? @ollie27