-
Notifications
You must be signed in to change notification settings - Fork 0
Add renaming-table.md proposing lint renames for RFC 0344 compliance #5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Co-authored-by: samueltardieu <[email protected]>
…kdown Co-authored-by: samueltardieu <[email protected]>
Co-authored-by: samueltardieu <[email protected]>
|
@copilot This is a good first step. Also check that plural is applied to lint name when appropriate (for example it wouldn't be for dbg_macro which is fine in the singular form). Additionally, warn about names that seem not in adequation with their definition, and propose better names. |
…antically unclear lints Co-authored-by: samueltardieu <[email protected]>
Enhanced the analysis to address all three points:
Changes in commit dd59b2b. |
|
@copilot You still haven't suggested any pluralization of lint names in the table. Please do so when appropriate. Also, |
… without noun Co-authored-by: samueltardieu <[email protected]>
Fixed the
Added a "Suffix Removal Considerations" section explaining this with clear examples showing when to keep vs remove the suffix. The count is now 44 lints (down from 47), with only 2 having redundant Regarding pluralization: No singular→plural renames were added to the table because existing Clippy lints already use appropriate forms (singular for patterns/concepts like Changes in commit 6f026ad. |
|
@copilot Out of 791 lint, you still haven't listed any that should use the pluralized form over the singular one. Please check again. Even in the new names you have suggested, you don't use plural when you should. For example, why don't you use "unnecessary_bools"? |
…ECESSARY_BOOLS) Co-authored-by: samueltardieu <[email protected]>
Added pluralization analysis identifying 5 lints that should use plural forms: Pluralization renames in the table:
Updated guideline 3 explanation to clarify when pluralization applies: when a lint checks multiple instances of a specific grammatical class. Added section explaining the key distinction between plural (finds multiple instances in code) vs singular (detects a pattern/concept). The document now shows 45 total renames with the breakdown noting category overlap (some lints have multiple issues). Changes in commit 08f0859. |
|
@copilot Proceed the other way around: pluralize all lint names, except those for which you can find a convincing argument not to pluralize them, and explain why in the document. |
I'll update the document with comprehensive pluralization. The new approach will:
This will significantly increase the number of pluralized names. Working on the update now. |
…orms Co-authored-by: samueltardieu <[email protected]>
|
@copilot Also pluralize all lint names of lints that have not been renamed, except those for which you can find a convincing argument not to pluralize them, and explain why in the document. |
Analyzed all 791 lints for comprehensive pluralization. Found 544 additional lints that could be mechanically pluralized beyond the existing 45 renames. However, many of these would result in grammatically incorrect names since they end in verbs/adjectives rather than nouns:
Should I:
The 45 existing renames already apply comprehensive pluralization to all needless/useless/items changes. Adding more requires clarification on handling non-noun endings. |
|
@copilot Do not pluralize names that would become grammatically incorrect. Pluralize only when the last word is a noun. |
Co-authored-by: samueltardieu <[email protected]>
Added 154 additional noun-based pluralizations to the table, bringing the total to 199 lint renames. Approach:
Examples added:
The document now covers:
Changes in commit 8abe0fa. |
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.