-
Notifications
You must be signed in to change notification settings - Fork 1k
Comment after associated type bound is incorrectly discarded #6815
Copy link
Copy link
Open
Labels
A-associated-type-boundsArea: associated type boundsArea: associated type boundsA-commentsArea: commentsArea: commentsC-bugCategory: this is a bug; use also I-* labels for specific bug kinds, e.g. I-non-idempotency or I-ICECategory: this is a bug; use also I-* labels for specific bug kinds, e.g. I-non-idempotency or I-ICEI-unexpectedly-removes-codeIssue: unexpectedly removes code that we should not be removingIssue: unexpectedly removes code that we should not be removing
Metadata
Metadata
Assignees
Labels
A-associated-type-boundsArea: associated type boundsArea: associated type boundsA-commentsArea: commentsArea: commentsC-bugCategory: this is a bug; use also I-* labels for specific bug kinds, e.g. I-non-idempotency or I-ICECategory: this is a bug; use also I-* labels for specific bug kinds, e.g. I-non-idempotency or I-ICEI-unexpectedly-removes-codeIssue: unexpectedly removes code that we should not be removingIssue: unexpectedly removes code that we should not be removing
Type
Fields
Give feedbackNo fields configured for issues without a type.
Summary
Forked out of #6234.
I tried to format this code:
Expected behavior
I expected to see this happen:
Actual behavior
Instead, this happened:
Configuration
rustfmtcli options used (if applicable):rustfmtconfiguration file (e.g.rustfmt.toml, if applicable): N/AReproduction Steps
Trivial.
Meta
rustfmt --version: