-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Render all trait bounds in where clauses in rustdoc #96680
Conversation
Some changes occurred in cc @camelid rustdoc-json-types is a public (although nightly-only) API. If possible, consider changing |
Thanks for opening it! So the zulip discussion about this is happening here. |
Regardless of what gets decided for the HTML, I think this would be great for JSON. |
My public API diffing and listing tool is based on rustdoc JSON and tries to represent items the same way as the HTML, to minimize user confusion. So if we only change this in rustdoc JSON, that use case can't be fulfilled any longer. So my preference would be to keep HTML and JSON in sync in this regard. |
☔ The latest upstream changes (presumably #96816) made this pull request unmergeable. Please resolve the merge conflicts. |
8c60416
to
cab38ee
Compare
This comment has been minimized.
This comment has been minimized.
cab38ee
to
15edd45
Compare
The job Click to see the possible cause of the failure (guessed by this bot)
|
I did not follow the zulip discussions. @GuillaumeGomez is the rustdoc team interested in landing this change, or should I close the PR? |
There doesn't seem to have a consensus based on what I can see from the zulip discussion. :-/ |
☔ The latest upstream changes (presumably #98279) made this pull request unmergeable. Please resolve the merge conflicts. |
I'm closing this PR. Please don't hesitate to ping me or pick it up if the consensus evolves. |
Split from #93803.
This PR modifies the rendering of bounds on generic parameters in rustdoc.
into
r? @GuillaumeGomez