KotlinSafeCallOperatorFilter should filter "unoptimized" chains #1818
+128
−13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For the following
Example.kt
Kotlin compiler versions
1.6.21
,1.7.21
,1.8.22
,1.9.22
,2.0.21
and2.1.0
producewhich is not handled by #1810
For the following
Example.kt
Kotlin compiler versions
2.0.21
and2.1.0
generate similarwhereas Kotlin compiler versions
1.6.21
,1.7.21
,1.8.22
,1.9.22
producewhich is handled by #1810
For https://github.com/SonarSource/sonar-kotlin/tree/2.22.0.5972
after #1810 we find 65 safe call operator chains
and after this change we find 78
ie 13 more.
For https://github.com/JetBrains/kotlin/tree/v2.0.0
after #1810 we find 2161
and after this 2275
ie 114 more.