[FIR] Improve UPPER_BOUND_VIOLATED message
Suggest removing explicit type arguments when the upper bound is a captured type since the only way to satisfy the upper bounds is by letting the type variable be inferred to its bound. #KT-65681 Fixed
This commit is contained in:
committed by
Space Team
parent
91e4837c95
commit
58264e177f
+1
@@ -691,6 +691,7 @@ object DIAGNOSTICS_LIST : DiagnosticList("FirErrors") {
|
||||
val UPPER_BOUND_VIOLATED by error<PsiElement> {
|
||||
parameter<ConeKotlinType>("expectedUpperBound")
|
||||
parameter<ConeKotlinType>("actualUpperBound")
|
||||
parameter<String>("extraMessage")
|
||||
}
|
||||
val UPPER_BOUND_VIOLATED_IN_TYPEALIAS_EXPANSION by error<PsiElement> {
|
||||
parameter<ConeKotlinType>("expectedUpperBound")
|
||||
|
||||
Reference in New Issue
Block a user