Mikhail Glukhikh 3fbb7bc920 K2: report MISSING_DEPENDENCY_CLASS in case of error type of expression ...

This commit is intended to get a more clear diagnostic in case when
the type checker creates an inconsistent error type due to some
classifier inaccessibility. Before this commit, we reported simply
ARGUMENT_TYPE_MISMATCH (see test). Now we report also
MISSING_DEPENDENCY_CLASS by analyzing an error type of a qualified
expression.

#KT-66356 Fixed

2024-03-18 18:11:14 +00:00

..

checkers-component-generator

[FIR][checkers][Wasm] Reorder information in messages for WRONG_JS_INTEROP_TYPE

2024-03-15 11:40:55 +00:00

checkers.js

[FIR][checkers][JS] Expand type aliases to supertypes in FirJsInheritanceClassChecker

2024-03-18 15:57:59 +00:00

checkers.jvm

[FIR] Remove FirNamedArgumentExpressions during completion

2024-03-13 17:05:48 +00:00

checkers.native

[FIR] Use proper directOverriddenFunctions fun in FirNativeThrowsChecker

2024-03-14 10:37:08 +00:00

checkers.wasm

[FIR][checkers][Wasm] Turn FirWasmJsInteropTypesChecker into a platform checker

2024-03-15 11:40:55 +00:00

checkers.web.common

[K/JS] Allow parameter properties inside external declarations ^KT-65965 Fixed

2024-02-29 09:46:59 +00:00

gen

Revert "Temporary: make PRE_RELEASE_CLASS a warning in both K1/K2 (KT-66551)"

2024-03-15 11:33:10 +00:00

src/org/jetbrains/kotlin/fir/analysis

K2: report MISSING_DEPENDENCY_CLASS in case of error type of expression

2024-03-18 18:11:14 +00:00

build.gradle.kts

Declare generated SourceSets correctly

2023-12-24 00:01:59 +00:00

module.md

[FIR] Part 5. Introduce paired common checkers for expect classes

2024-01-24 10:45:00 +02:00