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:
Mikhail Glukhikh
2018-11-29 14:31:37 +03:00
parent 1db7a0e0cc
commit c5c0cbccde
3 changed files with 19 additions and 41 deletions
@@ -1,3 +1,5 @@
// PROBLEM: none
class Test {
companion object {
fun f(x: Int, y: Int) = 1