...to avoid unexpected OOBE, which can happen if we incorrectly attempt
to load the first type argument of function type where the expected type
for the lambda doesn't have any!

^KTIJ-24743 Fixed

GitOrigin-RevId: 501c12868ddf6f23cebf527b61a030c862a1188b

GitOrigin-RevId: 3a8a180469e7fa861542dd7a8a87d162cd3dde7d

...as a common interface for fake light methods
* from source (UastFakeSourceLightMethod, e.g., local functions) or
* from descriptors (UastFakeDescriptorLightMethod in FE1.0, e.g.,
inline or deprecated-hidden functions in libraries)

so that they can share similar logics about annotations, in particular,
literally converting annotations on source or descriptors;
and adding an implicit nullability annotation.

GitOrigin-RevId: 038274b027311fc4855abc69986151be97a7b290

...to indicate these are fake light elemetns from source PSI

GitOrigin-RevId: a81ed75c5575d266f20953512d8978c732b39e5a

...to indicate these are fake light elements (from descriptors)

GitOrigin-RevId: 09771ff3f5b5f0f9e8171b30339af572c7f4e533

^KT-56728

GitOrigin-RevId: 5194ef6c9e6f58fd9df49e1bea7102c6788b5f4f

^KT-56728

GitOrigin-RevId: e6e679e7c9e9430ed393760451404f6f3a1cd0ca

GitOrigin-RevId: 264ca542d6dec38512a77ee9da40ab449f661869

^KTIJ-23301 fixed

GitOrigin-RevId: cbdac444e8c8192f467209db05e4da55bff38d2c

It's needed to test KTIJ-24413 fixes work in K1 and K2.

GitOrigin-RevId: 8a7ac5da385076df58979cf5663166eb096ba092

It's needed to test KTIJ-24413 fixes work in K2.

"// ALLOW_AST_ACCESS" added to multiDeclarationWithTypeParameters.kt
because test fails with "Access to tree elements not allowed".

GitOrigin-RevId: a2b417d7e9044b22df4e823a9a6d1292648e4fc2

^KTIJ-24585 Fixed

GitOrigin-RevId: 3e2b1de8b0b4823020e198ee5895fa5a92c95bf4

As a resolution scope for KtSourceModule, we should create `moduleWithDependenciesAndLibrariesScope` instead of an intersection scope. This is needed as the `GlobalSearchScope.contains` is slow for `GlobalSearchScope.union(moduleDependencies)`

^KTIJ-24670 fixed

GitOrigin-RevId: 99548ba87ea6b31aa560cbe7384733f200bda77a

A temporary solution to avoid exceptions in K2 IDE

GitOrigin-RevId: 003f65e3ed2bae4260b26c4493b57566d2bbd904

GitOrigin-RevId: 031e22b46e3f0aa2dd8935e2317a108331a1dd98

GitOrigin-RevId: 8b59ea0e96b26ba87c9959da234b22493e7d6081

GitOrigin-RevId: 5f905b5c68770330a8c567ed94b132751fbc7573

Apparently the logic was added to address IDEA-125376 because back then,
the line highlighter would be created in the editor markup. Nowadays, we
just use DocumentMarkupModel, so there's no need in recreating the
highlighter and the `openFileDescriptor` every time an editor with that
file is opened.

References:
  - IDEA-125376 Highlited current debug line disappear after switch between pages (Ctrl+E)

GitOrigin-RevId: d7778cf90c0c0c0dc3a14ce62f2ad6e266330ad9

GitOrigin-RevId: 17e955a080fe30685ce075d3bad2203f54af46fd

Instead of emitting elements of XSourcePosition type, which in our case
is always `this` anyway, make the `positionUpdateFlow` emit the
navigation mode to use with the updated position.

GitOrigin-RevId: 48a83890ccdf84f96c8617758e77c5b99e6c570f

This fixes the execution point highlighter not being updated after
loading a new disasm region finishes.

GitOrigin-RevId: 1fa1885efd0aa32c1918c8772a1ebb7ede937003

Use PositionPresentation directly, with separate flows for the main and
alternative source kinds.

GitOrigin-RevId: aa8783f219deb3cd75ee5e9861fde924fb5d2454

Launch the flow collectors tracking `activeSourceKindState`,
`navigationRequestFlow`, and `gutterIconRendererState` in the
coroutine scope defining the lifetime of ExecutionPointPresentation.
The scope is cancelled automatically at the right moment because of
the use of `.transformLatest {}`.

This also eliminates the need in clunky `.zipWithNext {}`, which used
to be used to call `hideAndDispose()` on the previous presentation.
The ExecutionPointPresentation is AutoCloseable now, and it is closed
when the coroutine scope is cancelled by the next element in the flow.

GitOrigin-RevId: 9966080e19c1555ad0dcabc62899321454e8c6b7

GitOrigin-RevId: bab244e5362ac1cad411ea5a7c75b6772bf4da04

GitOrigin-RevId: fadd59935d225fb6c0c6633b56a34e7c35b33c47

Wrap potentially erroneous operations with
`runCatching { }.getOrLogException(LOG)`,
like those accessing an XSourcePosition coming from the outside,

Otherwise, an unhandled exception in a flow operation fails the
collector coroutine and the piece of functionality the flow was
responsible for stops working.

GitOrigin-RevId: 31a8bfe4a3810101f0b8012a74312e205b36683b

GitOrigin-RevId: 0c6440d539fb468d584fcf8ffd76cb27b5e481d0

GitOrigin-RevId: 6a9e564d9520b638f29c7016fb2eb2d72dd9b5fd

GitOrigin-RevId: c04ccf80caa8916e0b84dc94ffa2c2d5706ae722

GitOrigin-RevId: 9ccb048946c0d75b75870adf91d691f0d6e9a090

GitOrigin-RevId: 72f518d2982b61c0b83cb960df3121e1b8bb9204

Navigating to the execution point is not implemented yet.

GitOrigin-RevId: 53c543b1349fb08e726d5301bae9035715d356ef

GitOrigin-RevId: 872f9b3eddad6253ea8669d45ff280ecff97365b

Now that there's no more need in our own logic responsible for scrolling
to the disasm position in an inactive disasm editor, the recently added
overload of `ExecutionPointHighlighter.show()` doesn't have to return
a Promise anymore.

GitOrigin-RevId: 82aa55c703b5b059406850ab8adba5e2252c05a2

GitOrigin-RevId: 775629e6eadd6b5c76d5163a1d4b5e8826444673

GitOrigin-RevId: 4d39baa001418f449cea24948df42d72ad7dae09

GitOrigin-RevId: 665be2d44a7520c0f1237eb59ee4660db2eeecf9

GitOrigin-RevId: deef2b7194fd65a7a43ac9bd9a53fbc97fce978b

GitOrigin-RevId: 7585a97463d0ca65a01e11315da8d8305582ab17