-
-
Notifications
You must be signed in to change notification settings - Fork 794
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
Do not report vararg arguments which are just passed to a vararg parameter #3157
Conversation
…as they do not create an array copy as of Kotlin 1.1 - Closes #3145
Codecov Report
@@ Coverage Diff @@
## master #3157 +/- ##
============================================
- Coverage 79.52% 79.50% -0.02%
- Complexity 2592 2596 +4
============================================
Files 437 437
Lines 7852 7861 +9
Branches 1495 1497 +2
============================================
+ Hits 6244 6250 +6
Misses 817 817
- Partials 791 794 +3
Continue to review full report at Codecov.
|
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.
In general I approve this PR. However, I wanted to raise the question, whether we want to support this rule without having type resolution enabled?
As long as our compiler plugin is not 1.0 and the changes are easy, I would say yes :) |
It appears this exception to the |
Yes it's correct. |
Yeah, I understand that is part of the plan for a 2.0 release. I just wanted to make sure that I wasn't missing anything based on the above comments about supporting this rule without type resolution. Our project currently does not use type resolution, so for the time being I am manually suppressing the rule for cases like this. Thanks for your response! |
This is one of the rule with "mixed behavior" (see more on #2994). Our take is that we will keep on supporting them for the time being, but will slowly transition to offer more and more Type Resolution capabilities. In other words: this rule could be converted to by a Type Resolution-only rule as part of our ongoing migration. |
Closes #3145