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
Interface Analyzer #8923
Interface Analyzer #8923
Conversation
Why do you add a new check instead of replacing the existing one? After all |
@rkapka because the interface itself could be nil, so running any receiver methods would create a panic |
Codecov Report
@@ Coverage Diff @@
## develop #8923 +/- ##
===========================================
- Coverage 60.89% 60.87% -0.02%
===========================================
Files 528 528
Lines 37336 37337 +1
===========================================
- Hits 22735 22729 -6
Misses 11344 11344
- Partials 3257 3264 +7 |
} | ||
if xIsIface && yIsNil { | ||
pass.Reportf(identX.Pos(), "A nilness check is being performed on an interface"+ | ||
", this check needs another accompanying check on the underlying object for the interface") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Little confusing. What does "another accompanying check" mean? Better to be specific
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice job!
What type of PR is this?
Feature
What does this PR do? Why is it needed?
equality checks are being compared.
Which issues(s) does this PR fix?
N.A
Other notes for review