-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Make the documentation of builtin macro attributes accessible #92456
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this comment make sense?
The items are hidden anyway, so it doesn't make any difference whether we inline them or not?
(Especially considering that
doc(inline)
is the default in this situation.)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, while this is currently true, I have to admit having chosen not to use
doc(inline)
explicitly since there is a change I've been considering to suggest to therustdoc
team, which would change, at the very least, the same-crate re-export of a#[doc(hidden)]
item when not using#[doc(inline)]
.For a crate wanting to feature
macro_export
-ed macros scoped within a module, currently, there are three options:Drawback:
__m__!
is visible at the crate root.Workaround: use js hacks to hide it in the aftermath (an ugly example)
Drawback: so hacky and ugly.
Another solution: use a helper crate that performs the
#[macro_export]
s, and thenpub use
them in a scoped fashion from the frontend crate (an example).Drawback: on top of being more cumbersome, it breaks
$crate
.The best solution for these things that occurred to me would be for
#[doc(inline)]
to override#[doc(hidden)]
(or have adoc(inline_unhidden)
for this, but that seems to be way more work). Indeed,doc(inline)
expresses an intent to have the item be documented in situ, so it makes sense to have it express_unhidden
semantics as well, for the rare case where it could matter.And this would be one such case, where we'd thus have not to use
doc(inline)
. I thus find it less error-prone to do it this way, if that makes sense?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I don't want to dig too much into this.