-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
Rustdoc json: Associated constants in impl have wrong representation #81340
Copy link
Copy link
Closed
Labels
A-rustdoc-jsonArea: Rustdoc JSON backendArea: Rustdoc JSON backendC-bugCategory: This is a bug.Category: This is a bug.T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.Relevant to the rustdoc team, which will review and decide on the PR/issue.requires-nightlyThis issue requires a nightly compiler in some way. When possible, use a F-* label instead.This issue requires a nightly compiler in some way. When possible, use a F-* label instead.
Metadata
Metadata
Assignees
Labels
A-rustdoc-jsonArea: Rustdoc JSON backendArea: Rustdoc JSON backendC-bugCategory: This is a bug.Category: This is a bug.T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.Relevant to the rustdoc team, which will review and decide on the PR/issue.requires-nightlyThis issue requires a nightly compiler in some way. When possible, use a F-* label instead.This issue requires a nightly compiler in some way. When possible, use a F-* label instead.
Type
Fields
Give feedbackNo fields configured for issues without a type.
This affects rustdoc json output
I expected to see this happen: The constant in the first impl is printed with
ItemEnum::Constant, the type and constant declaration inEasyToImplwithItemEnum::{AssocTypeItem, AssocConstItem}, and the corresponding type definition in the second impl withItemEnum::{Typedef, Constant}.Instead, this happened: The constant definitions in both impls are the odd one out. They uses the
ItemEnum::AssocConstItemform instead and their definitions are in thedefaultattribute.The raw json produced
Debug print of the item kinds in the impls
Meta
rustc --version --verbose: