FIR: add UnsafeCall resolution diagnostics
Previously unsafe call is reported as part of InapplicableWrongReceiver. This makes it difficult for the downstream checkers to report different diagnostics.
This commit is contained in:
committed by
Mikhail Glukhikh
parent
43a2ad0467
commit
6a03f31e50
+2
-1
@@ -13,7 +13,8 @@ enum class CandidateApplicability {
|
||||
INAPPLICABLE, // arguments have wrong types
|
||||
IMPOSSIBLE_TO_GENERATE, // access to outer class from nested
|
||||
RUNTIME_ERROR, // problems with visibility
|
||||
MAY_THROW_RUNTIME_ERROR, // unsafe call or unstable smart cast
|
||||
UNSAFE_CALL, // receiver nullability doesn't match
|
||||
MAY_THROW_RUNTIME_ERROR, // unstable smart cast
|
||||
CONVENTION_ERROR, // missing infix, operator etc
|
||||
RESOLVED_LOW_PRIORITY,
|
||||
RESOLVED_NEED_PRESERVE_COMPATIBILITY, // call resolved successfully, but using new features that changes resolve
|
||||
|
||||
Reference in New Issue
Block a user