Comment removed between type name and = #4244
Labels
a-comments
bug
Panic, non-idempotency, invalid code, etc.
good first issue
Issues up for grabs, also good candidates for new rustfmt contributors
hacktoberfest
help wanted
Milestone
This is one where I think a comment is justified; today we do not enforce such bounds (i.e. the compiler does not check that the right-hand side of a
type
definition actually conforms to such a bound), and the compiler actually errors if you try to include it (because we don't want people to mistakenly think that such bounds are enforced).But the comment here serves a useful purpose (about the intent, that we intend for this type definition to conform to the bound).
Originally posted by @pnkfelix in #2781 (comment)
The text was updated successfully, but these errors were encountered: