Alexander Udalov 84df996204 JVM IR: fix "step over" for inline function calls in conditions ...

Reimplement the same hacky approach used in the old backend (see
cc2fe6b0c6).

Previously, the debugger incorrectly stepped into Collections.kt on
"step over" inline function calls from stdlib like 'any'.

Since `if` and `when` expressions are represented the same way in IR,
the behavior is fixed for both of them. It's not the case in the old JVM
backend, where stepping over `when` conditions still suffers from the
same problem, which the newly added test checks.

2020-09-23 15:54:15 +02:00

..

ifConsts.kt

…

ifElse.kt

…

ifFalse.kt

…

ifFalseElse.kt

…

ifTrue.kt

…

ifTrueElse.kt

…

inlineCondition2.kt

Debugger, BE: Generate original line number after inlining if call is used in an if condition

2020-02-14 17:35:17 +09:00

inlineCondition.kt

JVM IR: fix "step over" for inline function calls in conditions

2020-09-23 15:54:15 +02:00

inlineLambdaObjectInit.kt

JVM: use precise line bounds when regenerating objects with no SMAPs

2020-05-19 18:33:27 +02:00

singleThen.kt

…

tryCatch.kt

…

when.kt

…