9 Commits

Author	SHA1	Message	Date
Kirill Rakhman	a63ec9efdc	[FIR] Implement warnings for java nullability upper bound violation	2023-11-15 08:43:55 +00:00
Mikhail Glukhikh	53d6ac24e5	Switch kotlin version to 1.7 ... * Change 1.6 to 1.7 constants * Fix SAFE_CALL_WILL_CHANGE_NULLABILITY for testData * Change EXPOSED_PROPERTY_TYPE_IN_CONSTRUCTOR_WARNING to EXPOSED_PROPERTY_TYPE_IN_CONSTRUCTOR_ERROR * Change NON_EXHAUSTIVE_WHEN_STATEMENT to NO_ELSE_IN_WHEN * Fix testData for SafeCallsAreAlwaysNullable * Change T -> T & Any in test dumps * Change INVALID_CHARACTERS_NATIVE_WARNING -> INVALID_CHARACTERS_NATIVE_ERROR * TYPECHECKER_HAS_RUN_INTO_RECURSIVE_PROBLEM_WARNING -> TYPECHECKER_HAS_RUN_INTO_RECURSIVE_PROBLEM_ERROR	2022-02-25 11:46:27 +00:00
Victor Petukhov	5326c875c0	Update compiler tests after rebase	2021-09-30 20:09:00 +03:00
Victor Petukhov	b957831683	Use WarningAwareUpperBoundChecker independently ... ^KT-47920 Fixed ^KT-48290 Fixed	2021-09-30 20:08:58 +03:00
pyos	9bb7a29baa	FIR: disregard enhancements for warnings ... Warnings are not implemented yet, so don't produce errors either.	2021-09-06 13:11:16 +03:00
pyos	03304bce96	FIR: enhance Java type parameter bounds ... This also fixes handling of self-recursive types. TODO: fix jspecify/{strict,warn}Mode/Captured.fir.kt	2021-09-06 13:11:08 +03:00
pyos	33251f6d50	Generate foreign annotation test data for FIR	2021-08-10 13:19:23 +03:00
Mikhael Bogdanov	cdbd0eb932	Reopen KT-47920 test and add missed .txt files ... #KT-47920 Open	2021-07-29 19:52:59 +02:00
Victor Petukhov	c5d783596d	Check type parameter bounds by java nullability annotations not only in basic resolution context ... ^KT-47920 Fixed	2021-07-29 14:23:55 +03:00