Redundant companion reference: simplify name conflict checking code
Before this commit, function with same name but different signature wasn't counted as name conflict, now it is - just because that exact check in this place could be too complex and error-prone Enhancement for KT-27539
This commit is contained in:
Vendored
+2
@@ -1,3 +1,5 @@
|
||||
// PROBLEM: none
|
||||
|
||||
class Test {
|
||||
companion object {
|
||||
fun f(x: Int, y: Int) = 1
|
||||
|
||||
Reference in New Issue
Block a user