Stabilize doc_cfg feature#79263
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 |
|
I think @Nemo157 is still working on some improvements to this - in particular, they're going to make it enabled by default whenever you use |
|
Then definitely (that would be so awesome!). Keeping this PR open in the meantime so no one else is tempted to open another one (including me hehe). |
|
Yeah, I'll try to get the PR to look at that up tomorrow. It'll probably need some testing with popular libraries and feedback whether it's a net positive (I was initially against it in the discussion on the tracking issue because I thought it would run into too many internal details, but with the ability to override the documented |
|
One thing I'm still slightly wary about is
Because most (all?) non-std users of this have been gating it to only run while building docs on docs.rs I don't know whether we know how this will affect them; it seems likely that this will result in some doctests silently not running. And personally what I need is the ability to gate individual doctests based on cfgs, not all doctests for a single item. |
Could we change the standard library to use |
|
For the curious: it looks like #79341 is the PR to make |
|
☔ The latest upstream changes (presumably #80965) made this pull request unmergeable. Please resolve the merge conflicts. |
|
I'm going to close this until we implement |
|
Given #89596 was merged, should this be re-opened? |
|
I think #90497 is a blocker for it. EDIT: nevermind, it should be ready now. |
Do you have an ETA for the new attempt at stabilizing |
|
I opened #100883. |
Fixes #43781
cc @Nemo157
cc @dtolnay
cc @rust-lang/rustdoc
r? @jyn514