azalea/kotlin-fork
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
99,029 Commits 1 Branch 0 Tags
45637c1b94de9509bcc242f797100e0ba4e4efd3
Commit Graph

69 Commits

Author SHA1 Message Date
Kevin Bourrillion 2694bdeb92 Change to use new JSpecify package location. 2022-12-27 11:10:59 +00:00
Kevin Bourrillion 671480ce1a Duplicate this entire test suite to jspecifyOld before changing the package locations in jspecify. 2022-12-27 11:10:59 +00:00
Denis.Zharkov cd0d6d2773 Adjust test data for postponing ProhibitUsingNullableTypeParameterAgainstNotNullAnnotated 
^KT-55357 Related
^KT-36770 Related
 2022-12-12 11:39:04 +00:00
pyos 6c6d653e85 FE: don't lose annotations on Java primitive arrays 
but only use them to enhance for warnings for now.

^KT-48861 Fixed
 2022-10-26 09:33:40 +02:00
Mikhail Glukhikh 730a5d1a88 FIR: introduce Java vs Kotlin class conflicts checker #KT-44441 Fixed 2022-07-04 13:28:58 +00:00
Ilya Chernikov bb996c1b27 Switch kotlin version to 1.8 
with appropriate fixes in testdata, tests and other
places.
 2022-06-29 10:20:30 +02:00
Jinseong Jeon a2da690afd Test: add java source files as JavaSourceRoot 
so that those can be properly populated in SingleJavaRootsIndex
 2022-06-16 22:14:17 +02:00
Denis.Zharkov f70ae2df3a FIR: Refine inference constraints when type variable in flexible position 
That issue might be fixed via changing
TypeVariableMarker.shouldBeFlexible at ConeConstraintSystemUtilContext
but this and some other tricks have been added because of incorrect
handling of constraints where type variable has a flexible bound

^KT-51168 Fixed
 2022-05-19 16:53:59 +00:00
Ivan Kochurkin c6f52893fb [FIR] Fix inconsistent RETURN_TYPE_MISMATCH and TYPE_MISMATCH reporting on functions and properties 
^KT-51203 Fixed
 2022-04-05 15:50:43 +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
Vladimir Dolzhenko 918a91dbdf Escape special names with backticks in test data 
#KT-51248
 2022-02-10 21:20:47 +00:00
Victor Petukhov 1f1b5256b0 Postpone type enhancement improvements till 1.7 due to some found broken cases unmarked by warnings before 
^KT-49378 Fixed
 2022-01-12 15:58:50 +03:00
Ivan Kylchik c7435ba760 Replace all occurrences of WITH_RUNTIME with WITH_STDLIB 
We are going to deprecate `WITH_RUNTIME` directive. The main reason
behind this change is that `WITH_STDLIB` directive better describes
its meaning, specifically it will add kotlin stdlib to test's classpath.
 2021-11-17 15:26:38 +03:00
Ivan Kochurkin d0a4ca199d [FIR] Add UNCHECKED_CAST 
Regenerate diagnostics code
 2021-11-12 15:20:45 +03:00
Dmitriy Novozhilov f26059a7d3 [FE] Add clear warning about future changes about nullability of safe call with non nullable receiver 
^KT-46860
 2021-10-27 16:28:37 +03:00
Victor Petukhov e0a4704c21 Revert "Make freshly substituted type variables def not nullable if they come from not null type parameter" 
This reverts commit 41936a790b37bef45d7e7dad851856ea1750ef01.
 2021-10-26 19:37:58 +03:00
Victor Petukhov 836c6b280d Make freshly substituted type variables def not nullable if they come from not null type parameter 
^KT-48778 Fixed
 2021-10-26 19:37:57 +03:00
Victor Petukhov d015d3bc0e Don't enhance previously erased value parameters for jspecify strict mode 
^KT-48261 Fixed
 2021-10-26 19:37:55 +03:00
Victor Petukhov b957831683 Use WarningAwareUpperBoundChecker independently 
^KT-47920 Fixed
^KT-48290 Fixed
 2021-09-30 20:08:58 +03:00
Victor Petukhov 70d70b9042 Use warn mode by default for jspecify nullability annotations in 1.6 
^KT-48851 Fixed
 2021-09-30 20:08:35 +03:00
Denis.Zharkov f7ef551f99 Report warnings on overrides with wrong types nullability 
^KT-48899 Fixed
 2021-09-30 14:36:26 +03:00
Denis.Zharkov 9ac29e0714 Fix enhancement when mixing TYPE_USE and non-TYPE_USE annotations 2021-09-28 22:59:18 +03:00
pyos 94402ba488 FE: prefer enhancements for errors over enhancements for warnings 2021-09-08 16:54:17 +03:00
pyos 8f699248f1 FE: force flexibility on unannotated ? 
TODO: unify this code with FIR

 #KT-48515 Fixed
 2021-09-08 16:54:17 +03:00
pyos afa1d18cc2 FE: in NullMarked scope, enhance T! to at least T 
#KT-44436 Fixed
 2021-09-08 16:54:17 +03:00
pyos f793afbfea FE: do not enhance ? into ? extends @NotNull Object in JSR-305 
This is already done in jspecify and makes more sense anyway.
 2021-09-08 16:54:17 +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 2847de10ac FIR: enhance Java super types 2021-09-06 13:11:09 +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 e2a48d3945 FIR: use frontend-independent Java type qualifier computation 2021-09-06 13:11:07 +03:00
pyos 5704dffdbe FIR: attach annotations to Java-converted cone types 2021-09-06 13:11:03 +03:00
pyos 5355d04553 FIR: enhance in/out-variant type arguments 2021-09-06 13:11:03 +03:00
pyos 8e122397b0 FIR: fix type index computation during enhancement 
1. in/out type parameters count;
2. star projections take up 1 space in the tree.
 2021-09-06 13:11:02 +03:00
Denis.Zharkov 4a9d4ed9fe Enable ProhibitUsingNullableTypeParameterAgainstNotNullAnnotated since 1.7 
^KT-36770 Fixed
 2021-08-31 15:41:17 +03:00
Denis.Zharkov 62bef48f9d Adjust test data to changed rendering: T!! -> T & Any 
^KT-26245 In Progress
 2021-08-31 15:41:15 +03:00
pyos 47d0211370 FE: do not enhance ? in jspecify NullMarked scope 
No clue whether this should be done for `@TypeQualifierDefault` since it
appears to have no specification whatsoever.

 #KT-48262 Fixed
 2021-08-18 16:41:00 +03:00
Mikhail Glukhikh dd3eb53904 Drop forgotten foreign annotation test data 2021-08-12 14:25:18 +03:00
pyos 623b289616 Regenerate foreign annotation test data for FIR 2021-08-11 15:58:02 +03:00
pyos 33251f6d50 Generate foreign annotation test data for FIR 2021-08-10 13:19:23 +03:00
pyos e2e0358505 Remove "FIR" foreign annotation tests 
They do not actually use FIR.
 2021-08-10 13:19:21 +03:00
Victor Petukhov 3eaa452f9e Take into account SimpleTypeWithEnhancement and subtyping related places 
^KT-47854 Fixed
 2021-08-04 17:36:50 +03:00
Dmitriy Novozhilov d17f984edf [FE 1.0] Migrate most of warning/error pairs to DiagnosticFactoryForDeprecation 2021-08-03 00:17:33 +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
Denis.Zharkov 8f484fcf88 Fix propagation of definitelyNotNull types from overrides 2021-07-29 19:45:57 +02:00
Denis.Zharkov f34726ff91 Fix test data for ForeignAnnotations 2021-07-29 19:45:56 +02:00
Victor Petukhov f84adcb378 [FE 1.0] Fix some foreign annotation tests 2021-07-29 19:45:56 +02:00
pyos c401582770 FE: do not wrap types with enhancements if they're the same 2021-07-29 14:52:51 +03:00
Victor Petukhov 5684b6977a Do preparation of enhancement as well (for types with enhancement), during subtype checks 
^KT-47899 Fixed
 2021-07-29 14:23:56 +03: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
Victor Petukhov f9cb0d61a8 Don't apply Java defaulting nullability annotations rules to unbounded wildcards 
^KT-47396 Fixed
 2021-07-29 14:23:53 +03:00