Change:
<ins> // Regression test for <https://github.com/rust-lang/rust/issues/108231>. // Macros with `#[macro_export]` attribute should be visible at the top level // even if they are inside a doc hidden item. #![crate_name = "foo"] // @has 'foo/index.html' // @count - '//*[@id="main-content"]//a[@class="macro"]' 1 // @has - '//*[@id="main-content"]//a[@class="macro"]' 'foo' #[doc(hidden)] pub mod __internal { /// This one should be visible. #[macro_export] macro_rules! foo { () => {}; } /// This one should be hidden. macro_rules! bar { () => {}; } } </ins>

Discussion:
<!-- Thank you for filing a regression report! A regression is something that changed between versions of Rust but was not supposed to. Please provide a short summary of the regression, along with any information you feel is relevant to replicate it. --I tried this code: I expected to see this happen: ! Instead, this happened: ! <!-- Provide the most recent version this worked on, for example: It most recently worked on: Rust 1.47 --It most recently worked on: Rust 1.67.1, Rust nightly-2023-02-03 <!-- Provide the version you are using that has the regression. --Rust nightly-2023-02-04 : modify labels: +regression-from-stable-to-nightly -regression-untriaged
Very likely regressed in (CC label T-rustdoc
So macros should be excluded from the inheritance as well. Sending a fix.

Code: Generated docs: ! So what I want to do is create a macro inside . I don't want it to show up in crate root - I want it only in this module. Both of the re-exports above work just fine. However, in the generated docs, one of them has no docs and the other doesn't show up at all. I'm surprised that is "recursive" - shouldn't it only hide and not hide ? Is this a bug? Versions:
Is there any news on this? We would like to use something like that for diesel to.
This doesn't appear to be just an issue with macros either: Produces entirely empty rustdoc output!
I have a similar issue with modules: Essentially I want to present nested module structure (that is used to limit visibility within crate) as non-nested in docs by leveraging re-exports. I'm thinking of that would override of the definition if applied to : Without this when inlining is used it creates confusion since the same module is both visible at the root of the crate and nested within submodule. This also confuses IntelliJ Rust, it shows 2 suggestions for imports all the time and could use this to hide one of them.
This is causing quite a big issue for Rocket's docs. We'd really like to export macros only from specific modules, but this bug makes it impossible without also exporting them at the root. Specifically, this: Results in: index: foo: Which is expected. Now, by adding to 's declaration/definition... ...all_ instances of in the docs disappear, even though is still reachable and not hidden!
Here's a macro that (sort of) patches around this issue: Simply wrap a declaration with : One must be careful not to use features in expansion arms. As long as this issue exists, the macro will appear as in the right place without a docstring. Should this issue be fixed, nightly and stable docs will match.
It looks like this issue has been inactive for a while, but the problem is still there. I would like to know if there are more comments from members about said he had a discussion with and about this, but I didn't find it. that it looked fine to him.
I'm no longer a member of the rustdoc team, please don't ping me.

Technical information for everyone following this issue: I'm working on it (well, you can infer that from my PRs I suppose). One of the last blockers is actually : currently we merge both the 's and the item's attributes. Meaning that the is inherited. The problem is that it's currently not possible to filter the sub-attributes of an (for example, in , we want to keep ). So hopefully, once I figure out this part, I should be able to fix all the remaining issues at once.
So now only one issue remains:
FWIW, "back in the day" I did have a branch with an implementation tackling your situation, if you are interested:
I have a vague idea on how to fix it but I'm definitely interested into seeing how you did it. You sure you don't want to send a PR btw?