-
Notifications
You must be signed in to change notification settings - Fork 583
Document how lints are actually emitted #1168
Copy link
Copy link
Open
Labels
A-lintsArea: lintsArea: lintsC-enhancementCategory: enhancementCategory: enhancementE-hardDifficulty: might require advanced knowledgeDifficulty: might require advanced knowledgeE-needs-investigationCall for participation: this issue needs further investigationCall for participation: this issue needs further investigationT-compilerRelevant to the compiler teamRelevant to the compiler team
Description
Metadata
Metadata
Assignees
Labels
A-lintsArea: lintsArea: lintsC-enhancementCategory: enhancementCategory: enhancementE-hardDifficulty: might require advanced knowledgeDifficulty: might require advanced knowledgeE-needs-investigationCall for participation: this issue needs further investigationCall for participation: this issue needs further investigationT-compilerRelevant to the compiler teamRelevant to the compiler team
Type
Fields
Give feedbackNo fields configured for issues without a type.
The section on linting describes how to declare a lint and how lint passes are constructed, but we are still missing an explanation on how the lint system takes buffered lints and decides whether to actually emit them to users. For instance, how does
--cap-lintswork?