Fix incorrect diagnostic message for CONFLICTING_OVERLOADS

- the member and the container were mixed up - don't output "defined in" part of the message, because we tell later where it's already defined in - fix an instability of the diagnostic order in OverloadResolver by using LinkedHashSet
2014-04-08 22:57:04 +04:00
parent 0d90dcf010
commit 4f9f5d231b
8 changed files with 47 additions and 10 deletions
@@ -0,0 +1,7 @@
+// !DIAGNOSTICS_NUMBER: 2
+// !DIAGNOSTICS: CONFLICTING_OVERLOADS
+
+class conflictingOverloads {
+    fun lol(x: Int) = x
+    fun lol(y: Int) = y
+}
@@ -0,0 +1,10 @@
+<!-- conflictingOverloadsClass1 -->
+<html>
+'<b>
+internal</b>
+ <b>
+final</b>
+ <b>
+fun</b>
+ lol(x: kotlin.Int): kotlin.Int'<br />
+is already defined in conflictingOverloads</html>
@@ -0,0 +1,10 @@
+<!-- conflictingOverloadsClass2 -->
+<html>
+'<b>
+internal</b>
+ <b>
+final</b>
+ <b>
+fun</b>
+ lol(y: kotlin.Int): kotlin.Int'<br />
+is already defined in conflictingOverloads</html>