You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know the displaying of #[repr(...)] in general has some issues, and this certainly seems related.
Currently the aliased type is stored as a TypeAliasInnerType, which does not have enough info to find the original ADT and render the repr (or other attributes, for that matter). For example:
The example also hits #66401, so I think the proper solution is to really use the exact same rendering code for the aliased types as for the original type. That prevents such mismatches, though I may be missing why that was not done in the first place, maybe there is a good reason.
The text was updated successfully, but these errors were encountered:
rustbot
added
needs-triage
This issue may need triage. Remove it if it has been sufficiently triaged.
T-rustdoc
Relevant to the rustdoc team, which will review and decide on the PR/issue.
labels
May 7, 2025
I know the displaying of
#[repr(...)]
in general has some issues, and this certainly seems related.Currently the aliased type is stored as a
TypeAliasInnerType
, which does not have enough info to find the original ADT and render the repr (or other attributes, for that matter). For example:where
Foo
is rendered asbut on the docs page for
Bar
it isThe example also hits #66401, so I think the proper solution is to really use the exact same rendering code for the aliased types as for the original type. That prevents such mismatches, though I may be missing why that was not done in the first place, maybe there is a good reason.
@rustbot label +T-rustdoc
The text was updated successfully, but these errors were encountered: