-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Rustdoc should not generate docs for hidden methods. #34025
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
Comments
Could you provide a short example on which I could easily please? As far as I can tell, |
Also, I made a patch which is supposed to fix this. Can you test it please? make check-stage1-rustdocck && cd src/librustdoc/ && ../../x86.../stage1/bin/rustdoc [path of the crate you want to generate] -o [output dir] |
I will take a look at doing both of these in a moment when I get back to a
|
If you prefer that I test it, I'll need a short example like I said. So either way, I'm waiting. 😉 |
So far I haven't managed to trigger it outside of that project, If i get a usable test case I'll post it. |
I think I've got a nice small test case now, I'll post it to github in a moment but the gist is:
|
Test case is here: https://github.com/BenTheElder/docs_test_case |
Thanks! Testing my patch. |
It doesn't work. But now I know what to look! :) |
Of course! Thanks for looking.
|
@BenTheElder: Take a look to the PR linked. |
Thanks, pulling your fix now to test.
|
I think the PR works, i did:
Which seems to produce the expected page in |
Should be fixed by #34045. |
rustdoc: Don't generate empty files for stripped items We need to traverse stripped modules to generate redirect pages, but we shouldn't generate anything else for them. This now renders the file contents to a Vec before writing it to a file in one go. I think that's probably a better strategy anyway. Fixes: #34025
See previous discussion here: #34023 (comment)
rustdoc seems to be building files for methods marked
#[doc(hidden)]
in rust 1.9.0 and nightly but not in 1.8.0, observed with code generated when building opencv-rust.It seems that these methods should be ignored.
The text was updated successfully, but these errors were encountered: