KT-1138 Need better diagnostic for case when method/constructor call is followed by class initializer or simple block
This commit is contained in:
@@ -0,0 +1,29 @@
|
||||
//+JDK
|
||||
|
||||
class Foo() {
|
||||
private val builder = StringBuilder("sdfsd");
|
||||
|
||||
{
|
||||
}
|
||||
}
|
||||
|
||||
class Foo1() {
|
||||
private val builder = <!NONE_APPLICABLE!>StringBuilder<!>("sdfsd")
|
||||
|
||||
<!DANGLING_FUNCTION_LITERAL_ARGUMENT_SUSPECTED!>{
|
||||
}<!>
|
||||
}
|
||||
|
||||
fun foo() = {
|
||||
<!NONE_APPLICABLE!>println<!>(1)
|
||||
<!DANGLING_FUNCTION_LITERAL_ARGUMENT_SUSPECTED!>{}<!>
|
||||
}
|
||||
|
||||
fun foo1() = {
|
||||
println(1);
|
||||
{}
|
||||
}
|
||||
|
||||
fun println(<!UNUSED_PARAMETER!>i<!> : Int) {}
|
||||
fun println(<!UNUSED_PARAMETER!>s<!> : Byte) {}
|
||||
fun println() {}
|
||||
@@ -32,7 +32,7 @@ fun main(args : Array<String>) {
|
||||
<!UNRESOLVED_REFERENCE!>a<!>.foo1()(<!UNRESOLVED_REFERENCE!>a<!>)
|
||||
|
||||
foo2()({})
|
||||
foo2()<!TOO_MANY_ARGUMENTS!>{}<!>
|
||||
foo2()<!TOO_MANY_ARGUMENTS, DANGLING_FUNCTION_LITERAL_ARGUMENT_SUSPECTED!>{}<!>
|
||||
(foo2()){}
|
||||
(foo2())<!TYPE_MISMATCH!>{<!CANNOT_INFER_PARAMETER_TYPE!>x<!> -> }<!>
|
||||
foo2()(<!TYPE_MISMATCH!>{<!CANNOT_INFER_PARAMETER_TYPE!>x<!> -> }<!>)
|
||||
|
||||
@@ -13,5 +13,5 @@ fun test() {
|
||||
v1({}, <!ERROR_COMPILE_TIME_VALUE!>1<!>, {})
|
||||
v1({}, {}, {it})
|
||||
v1({}) <!VARARG_OUTSIDE_PARENTHESES!>{}<!>
|
||||
v1 <!VARARG_OUTSIDE_PARENTHESES!>{}<!>
|
||||
v1 <!VARARG_OUTSIDE_PARENTHESES, DANGLING_FUNCTION_LITERAL_ARGUMENT_SUSPECTED!>{}<!>
|
||||
}
|
||||
Reference in New Issue
Block a user