Uh oh!
There was an error while loading. Please reload this page.
Create rustdoc_internals feature gate - #90420
Conversation
rust-highfive
commented
Oct 30, 2021
(rust-highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
camelid
commented
Oct 30, 2021
r? @camelid |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
jyn514
commented
Oct 30, 2021
This seems ... kind of unnecessary to me? We can document on the tracking issues that these aren't meant to be stabilized, I don't think it also needs to be in the source code of everything using them. And as you've noticed the logic for |
The standard library often uses the naming convention of If merging the feature gates would be too complicated, I'm okay to leave them separate, but I would prefer to merge them and make it clear in the name that they are internal-only.
They're only used in the standard library and rustdoc IIUC, and this would reduce the number of feature gates necessary? |
jyn514
commented
Oct 30, 2021
Hmm, ok, seems reasonable. |
This comment has been minimized.
This comment has been minimized.
e2a9da8 to
10039e2Compare
This comment has been minimized.
This comment has been minimized.
10039e2 to
dc4ab79CompareUh oh!
There was an error while loading. Please reload this page.
dc4ab79 to
081e0cfCompareGuillaumeGomez
commented
Nov 8, 2021
Updated the message and set the PR as ready to review. |
This comment has been minimized.
This comment has been minimized.
081e0cf to
e8a9813Compare
This comment has been minimized.
This comment has been minimized.
e8a9813 to
bcd821eCompare
This comment has been minimized.
This comment has been minimized.
bcd821e to
987b6daCompare6041272 to
ce7f8a0CompareGuillaumeGomez
commented
Nov 19, 2021
Done! |
camelid
left a comment
There was a problem hiding this comment.
Left a few comments. r=me after fixing those.
There was a problem hiding this comment.
This is in the wrong section; it should be next to doc_notable_trait.
There was a problem hiding this comment.
Also, can you create an actual tracking issue? We shouldn't just link to this PR.
There was a problem hiding this comment.
nit:
| /// Allows using doc(primitive) without a future-incompat warning | |
| /// Allows using `doc(primitive)` without a future-incompat warning |
ce7f8a0 to
5dbcc0cCompare
It does link to the tracking issue. Unless I missed something? Otherwise, I updated following your comments. |
camelid
commented
Nov 21, 2021
Sorry, maybe GitHub glitched and showed me the wrong page. Tracking issue looks good to me. |
camelid
left a comment
There was a problem hiding this comment.
r=me with these two comments fixed
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
5dbcc0c to
9447d1fCompareGuillaumeGomez
commented
Nov 24, 2021
@camelid Your comments made perfect sense (and I have no clue how I messed up the indent...). Updated! |
camelid
commented
Nov 24, 2021
Thanks! @bors r+ rollup |
bors
commented
Nov 24, 2021
📌 Commit 9447d1f has been approved by |
…ature, r=camelid Create rustdoc_internals feature gate As suggested by `@camelid` [here](rust-lang#90398 (comment)), since `doc_keyword` and `doc_primitive` aren't meant to be stabilized, we could put them behind a same feature flag. This is pretty much what it would look like (needs to update the tests too). The tracking issue is rust-lang#90418. What do you think `@rust-lang/rustdoc` ?
…laumeGomez Rollup of 7 pull requests Successful merges: - rust-lang#89542 (Partially stabilize `duration_consts_2`) - rust-lang#90044 (Restrict aarch64 outline atomics to glibc for now.) - rust-lang#90420 (Create rustdoc_internals feature gate) - rust-lang#91075 (Reduce prominence of item-infos) - rust-lang#91151 (Fix test in std::process on android) - rust-lang#91179 (Fix more <a> color) - rust-lang#91199 (rustdoc: Add test for mixing doc comments and attrs) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
As suggested by @camelidhere, since
doc_keywordanddoc_primitivearen't meant to be stabilized, we could put them behind a same feature flag.This is pretty much what it would look like (needs to update the tests too).
The tracking issue is #90418.
What do you think @rust-lang/rustdoc ?