GitOrigin-RevId: c989e0611834bc24fc8768d648a0c8bf1b285078

GitOrigin-RevId: 615229681afabbfafaf4a37f13d90a48c6e79638

GitOrigin-RevId: 95ab6b6c991593eba437f27a3f40847438278170

In "Allow facade with forced platform for JVM-modules" by Dmitry Savvinov, KotlinCacheServiceImpl API slightly changed, so new code there had to be adapted accordingly.

GitOrigin-RevId: 2d4346a82ea46527241da431918d1f004d7ac96a

GitOrigin-RevId: f138761576ac873e6e4aaabb27cdcc8ccacac7bf

As 'kotlin-script-runtime' is also used by the Python plugin, it's not possible to safely advance it to a bootstrap version. So, like with kotlinc.kotlin-stdlib and kotlinc.kotlin-reflect, the new 'kotlinc.kotlin-script-runtime' library comes as a Kotlin-local replacement.

GitOrigin-RevId: 9f1537709f249d9c43861c79f6e2148041822222

'kotlin-script-runtime' is used not only in the Kotlin plugin, but also in Python modules. This commit introduces a Kotlin-local version of kotlin-script-runtime.

GitOrigin-RevId: 2f2ea6ad0b9d2a0cfaea09b1eaef512517241b79

There's a new Kotlin artifact appeared after moving the JPS plugin to the compiler repository.

GitOrigin-RevId: 6f0818b7630e7efcb34875ba0c0fe074fc0766d1

GitOrigin-RevId: d405b4c342ec18599de5da30faae3136c3ece2a5

GitOrigin-RevId: 495d180e27a0554f290abb6ac96651fb4c37e2f5

GitOrigin-RevId: 78a09631c16bfda98f85d59eeca3f0943a257b78

See 14452661cce44f75ab0683aa0462ce396416a053 in kotlin repo

GitOrigin-RevId: 353d0454d189b53cd0ba2842f3198545c9f0e638

The action was initially introduced during early stages of COMPOSTE mode
development, to alleviate faster testing/prototyping roundtrip. Now,
with HMPP becoming the default mode, it is obsolete and essentially
unused

GitOrigin-RevId: 3e88367867e9de360b5941a2d694a60e8fb0f4e1

GitOrigin-RevId: cde8eafb7bd7f4dd7afc8a53a38041951ce8e1dd

KotlinHighLevelFunctionParameterInfoHandler: Use new KtCallResolver.resolveCandidates() API to get all candidates.

GitOrigin-RevId: d25c80c610a3fb4097b3e82863bba57d9f4dadb2

This partially reverts adbe14aa

^KT-51112 Fixed

GitOrigin-RevId: 605c78ef59fbbbf36374e1b031b28bbc57c7338f

GitOrigin-RevId: bed82ab1e629068fe5b854c3bba5142ed8ebaa4b

GitOrigin-RevId: 2155091eb7b4f4ee5905c6d817de28ed47b0943c

GitOrigin-RevId: f9629b64da5988e10cdb84b5aa379f63b0c4a927

GitOrigin-RevId: b94615550722a29a88c587b27fa15c49d9e7ea71

This shares most of the implementation across FE10 and FIR.

GitOrigin-RevId: 5973249bd7d1874cc2f9c3955def48845b86c2c1

GitOrigin-RevId: f119bab48a15dd639827d865e479abae17374083

Using `-Xenhance-type-parameter-types-to-def-not-null` compiler
argument, it is possible to enable Java `@NotNull` type enhancement to
definitely non-nullable types while the language feature
`DefinitelyNonNullableTypes` is still disabled (e.g., when the language
version is set to 1.6).

In this case, the "Change parameter type"/"Change type" quick fixes do
nothing instead of changing the type `T` to `T & Any`, as the `T & Any`
type is resolved not as a DNN type but as a regular type parameter `T`.

This commit adds an explicit check for the state of
`LanguageFeature.DefinitelyNonNullableTypes`, so the useless fix is
not proposed to the user.

^KTIJ-20981

GitOrigin-RevId: a249bdd00042261904aaf38c95850093079ee5ce

Updated two incorrectly fixed tests.

^KTIJ-20990 Fixed

GitOrigin-RevId: e40e5f30ac957157d7b7fd0a9c881e00c56b49cf

Updated in `kt-212-master` tests to reflect recent changes in the compiler.

1. Removed `-Xopt-in` command line argument, use `-opt-in` everywhere in
the `quickfix/experimental` test suite. Removed a test that became
duplicating after the change.

Corresponding commit in the compiler: eeadd8588dfe8284c1c1ab1275b87661db5c1001

2. Removed a test that become obsolete after reverting
`OPT_IN_MARKER_ON_OVERRIDE` limitation.

Corresponding commit in the compiler: c2f43dd98e4ceadd5cf5b6d81bca212e36c6a284

^KTIJ-20990 Fixed

GitOrigin-RevId: a19946f1a09d8d264cab04dc7099bcbe263ebff4

GitOrigin-RevId: 68b0d05bd24981d3a93e276665925608b9ab080d

Current and previous versions are both incorrect and probably synthetic property access should be handled separately

GitOrigin-RevId: 7f0d488ccf3aed19ca25bdeea1e0e3bae1344087

GitOrigin-RevId: 31917998d524f2b14cffdd5825063f7a8c97cdc1

GitOrigin-RevId: bc642d9a17a5e12e83cae53ba3668b13d0740ebd

The super type calls now resolve to the constructor they are
calling instead of the class.

GitOrigin-RevId: 4d792e8a2b2eb95bcc49ff9cf46448388b21094e

GitOrigin-RevId: df1e7fd5854eaef52a085bc445544a2bbd58f54f

GitOrigin-RevId: 33ec443e1cc5537ef16f9f388deac97e457e4fc1

GitOrigin-RevId: 0677cf10f3b7d112cd3be4ea043f2d0a88f35f52

- Use `KtVariableLikeSignature.name` instead of `symbol.name` to show the name
of the parameter with respect to `@ParameterName` annotations
- Temporarily disable insertion handling of the `CallableKind.ReceiverCastRequired`
(the insertion of the `(foo as Bar)` after the completion), since right now
it is triggered for any member of any generic type due to use-site substitution
overrides unwrapping (see KtSymbolByFirBuilder.unwrapUseSiteSubstitutionOverride).
The tracking issue for this is KTIJ-20913
- Update testData for completion and insertion handling tests
which do not pass in FIR due to the aforementioned changes

GitOrigin-RevId: 360ee761d2d8b3e27075f91e442a0c3e1b39355b

GitOrigin-RevId: bf7ee8d7e3d6be659ac8134f80d57f6267e0bc98

GitOrigin-RevId: 75eb5ad777e55f940c055334d068ae17b18384cb

GitOrigin-RevId: 2680ef06a606a0f21e7b1e36bee27a670de8279f

GitOrigin-RevId: 4b951cfa3301537822294cac6427c8e6146f0194

As there currently are no other kinds of intersection types except
definitely non-nullable types, there is no need to check that the
intersection type is a DNN type. This commit removes these checks in
the type highlighting visitor.

^KTIJ-20253 Fixed

GitOrigin-RevId: c3e3da0c783f2c37b9bacf9f43fc38e5d2b8be51

GitOrigin-RevId: 8142b35d9b55e899fe81491e9938774b0120252a