Skip to content

Feature: Request to Integrate NilAway into golangci-lint for Enhanced Nil Panic Detection #4211

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

Closed
mfreeman451 opened this issue Nov 19, 2023 · 3 comments
Labels
declined enhancement New feature or improvement

Comments

@mfreeman451
Copy link

Your feature request related to a problem? Please describe.

I would like to propose the integration of NilAway, a sophisticated static analysis tool, into golangci-lint. NilAway is designed to enhance the reliability of Go programs by detecting potential nil panics at compile time, thus significantly reducing the likelihood of runtime panics related to nil references.

Describe the solution you'd like.

  1. Seamless Integration: NilAway should be integrated as one of the linters within golangci-lint. It should be easily enabled or disabled in the .golangci.yml configuration file, similar to other linters. This integration would allow users to run NilAway checks alongside other linters in a single, unified workflow.
  2. Configuration Compatibility: Users should be able to configure NilAway settings directly through the .golangci.yml file. This approach ensures that all linter configurations are centralized and easily manageable.

Describe alternatives you've considered.

Using NilAway as a standalone tool

Additional context.

No response

@mfreeman451 mfreeman451 added the enhancement New feature or improvement label Nov 19, 2023
Copy link

boring-cyborg bot commented Nov 19, 2023

Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors.

@mfreeman451
Copy link
Author

PR submitted #4212

@ldez
Copy link
Member

ldez commented Nov 19, 2023

Duplicate of #4045

@ldez ldez marked this as a duplicate of #4045 Nov 19, 2023
@ldez ldez closed this as completed Nov 19, 2023
@ldez ldez added the declined label Nov 19, 2023
@golangci golangci locked as resolved and limited conversation to collaborators Nov 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
declined enhancement New feature or improvement
Projects
None yet
Development

No branches or pull requests

2 participants