Skip to content

Conversation

ldez
Copy link
Member

@ldez ldez commented Oct 13, 2025

Related to #6123
Related to #686

@ldez ldez added this to the unreleased milestone Oct 13, 2025
@ldez ldez added the linter: new Support new linter label Oct 13, 2025
@ldez ldez force-pushed the feat/modernize branch 2 times, most recently from 6067bf6 to b9b3d11 Compare October 13, 2025 04:17
Copy link
Member

@bombsimon bombsimon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dang, that's a lot of test cases, nice! ⭐

I noticed there's 100 comments saying nope and 24 saying noop (x2 for the fixed version). Is this intentional? I guess noop would make more sense since there's no operation from any analyzer in those scenarios.

Also super nit, but there's a mix between Nope., nope: and nope, prefixed lines where we don't expect any diagnostic.

Of course, none of this is something I would block on and the clarification to why they don't have any diagnostic is what matters!

@ldez
Copy link
Member Author

ldez commented Oct 13, 2025

The test files are from x/tools with some adaptations; I don't want to change them too much.

https://github.com/golang/tools/tree/f1d1a69984531871c04f9fb4f5c8971d0d00a86b/go/analysis/passes/modernize/testdata/src

@ldez ldez merged commit 655e8ed into golangci:main Oct 13, 2025
18 checks passed
@ldez ldez deleted the feat/modernize branch October 13, 2025 19:56
- '^math\.'
- '^http\.StatusText$'

modernize:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great to finally see this in here! 🚀 What are the default values for this linter?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

linter: new Support new linter

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants