-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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: add support for incoherent impls on structs and traits #103746
rustdoc: add support for incoherent impls on structs and traits #103746
Conversation
r? @jsha (rustbot has picked a reviewer for you, use r? to override) |
// * https://github.com/rust-lang/rust/issues/103170 — where it didn't used to get documented | ||
// * https://github.com/rust-lang/rust/pull/99917 — where the feature got used | ||
// * https://github.com/rust-lang/rust/issues/53487 — overall tracking issue for Error | ||
if tcx.has_attr(did, sym::rustc_has_incoherent_inherent_impls) { |
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.
Then the issue will remain for the JSON output if we fix it in inline
, no?
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 is only a problem in the HTML output because, if inlining isn’t performed, there’s nowhere to actually show it. JSON directly represents impl blocks as their own item, rather than attaching them to their types, so all it needs to do is not strip them out.
If there’s a problem in JSON output, the solution is going to be totally different and should probably be a separate PR.
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.
Makes sense! So no need for it.
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.
Probably still want to add a test case for JSON output on incoherent impl, but, again, separate PR.
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.
Yes, totally fine.
Thanks! @bors r+ rollup |
…-trait, r=GuillaumeGomez rustdoc: add support for incoherent impls on structs and traits Fixes rust-lang#103170
Rollup of 8 pull requests Successful merges: - rust-lang#97971 (Enable varargs support for calling conventions other than C or cdecl ) - rust-lang#101428 (Add mir building test directory) - rust-lang#101944 (rustdoc: clean up `#toggle-all-docs`) - rust-lang#102101 (check lld version to choose correct option to disable multi-threading in tests) - rust-lang#102689 (Add a tier 3 target for the Sony PlayStation 1) - rust-lang#103746 (rustdoc: add support for incoherent impls on structs and traits) - rust-lang#103758 (Add regression test for reexports in search results) - rust-lang#103764 (All verbosity checks in `PrettyPrinter` now go through `PrettyPrinter::should_print_verbose`) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
…Simulacrum [stable] 1.67.0 release Last minute backports: * rustdoc: add support for incoherent impls on structs and traits rust-lang#103746 r? `@ghost`
…mulacrum [beta] branch 1.66 This PR: * Bumps version placeholders * Bumps CI channel to beta * Backports "rustdoc: add support for incoherent impls on structs and traits rust-lang#103746"
Fixes #103170