-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Rustdoc does not show bounds on associated items in the declaration of re-exported traits #84579
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Ooooh, it works on |
I may have found the reason why we are skipping the associated type binding. So when an external item (in our case an associated type) gets documented it goes through rust/src/librustdoc/clean/mod.rs Lines 1015 to 1016 in ff2c947
Further down we get to: rust/src/librustdoc/clean/mod.rs Line 1102 in ff2c947
which produces (for the
Then rust/src/librustdoc/clean/mod.rs Line 1102 in ff2c947
Output
The last rust/src/librustdoc/clean/mod.rs Lines 1106 to 1112 in ff2c947
Afaics, the reason the unexported trait gets properly "documented" is because a different code path is run which doesn't involve clean on a |
Uh oh!
There was an error while loading. Please reload this page.
Currently on nightly the declaration for
IntoIterator
looks like:While the actual declaration with attributes stripped is:
Previously up till 1.48.0 this rendered as:
Which is not great, but at least it has the information there. I tried to identify the PR which changed this in 1.49.0, but skimming the list from a few search queries none of them stood out to me.
The text was updated successfully, but these errors were encountered: