-
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
rustdoc: make --passes
and --no-defaults
have no effect
#91900
Conversation
r? @jyn514 |
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.
This looks great, thanks!
msg.help("`#![doc(no_default_passes)]` no longer functions; you may want to use `#![doc(document_private_items)]`"); | ||
} else if name.starts_with("passes") { | ||
msg.help("`#![doc(passes = \"...\")]` no longer functions; you may want to use `#![doc(document_private_items)]`"); |
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.
Ugh, not super happy that this can be configured both through attributes and a CLI flags ... but that's a fight for another day.
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.
This looks great! Can you just squash the commits into one? Then it looks to good to merge once the FCP in #91714 finishes :)
- flags no longer function, see #44136 - adjust tests to match new behavior - removed test issue-42875 (covered regression with --no-defaults) - moved input-format to removed flags - move all removed flags to bottom - note flag removal in command help - remove DefaultPassOption enum (now redundant with `show_coverage`)
FCP has completed! @rustbot ready |
@bors r+ |
📌 Commit 02b94b7 has been approved by |
☀️ Test successful - checks-actions |
Thanks for working on this! |
Finished benchmarking commit (940a97a): comparison url. Summary: This change led to moderate relevant mixed results 🤷 in compiler performance.
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression |
Fixes #91714
One potential issue is that currently there is no stable way to achieve
--document-hidden-items
. This affects testissue-15347
.I also had to modify the tests
issue-42875
andno-compiler-export
. Regardless of combinations of--document-hidden-items
and--document-private-items
, I was unable to get these to pass without the modifications. I left behind a comment noting the change.