[FIR] KT-54978 Prohibit explicit type arguments in property accesses
- Add a checker which ensures that property accesses have no explicit type arguments. If an error on the property access's callee reference already exists, the new error is not reported in favor of the existing error, as the property access may have been intended to be a function call. - `complicatedLTGT.fir.kt`: The underlying parser issue is not yet solved, which is why `x` is parsed as a property access with explicit type arguments. - `reservedExpressionSyntax` tests: This new check makes a lot of the access expressions in these tests illegal, so valid lines have been added and invalid lines appropriately marked with `EXPLICIT_TYPE_ARGUMENTS_IN_PROPERTY_ACCESS` errors. ^KT-54978 fixed
This commit is contained in:
committed by
teamcity
parent
4d20b43619
commit
d4e6a4ad54
+1
@@ -16,6 +16,7 @@ package test {
|
||||
public final val test1: () -> test.Right
|
||||
public final val test1a: () -> test.Right
|
||||
public final val test2: () -> test.Right
|
||||
public final val test2a: () -> test.Right
|
||||
public final val </*0*/ T> kotlin.collections.List<T>.b: kotlin.Int
|
||||
public final val kotlin.Int.c: kotlin.Int
|
||||
public open override /*1*/ /*fake_override*/ fun equals(/*0*/ other: kotlin.Any?): kotlin.Boolean
|
||||
|
||||
Reference in New Issue
Block a user