Mikhael Bogdanov 02d9c526e2 Proper resort variables on inlining lowered ir closures ...

Original problem is that lowered ir closures doesn't meet inliner expectations
 about captured variable position in inlining method.
 E.g.: Call 'foo(valueParam) { capturedParam }' to
  inline function 'foo' with declaration

      inline fun foo(valueParam: Foo, inlineParamWithCaptured: Bar.() ->) ....

 is reorganized through inlining to equivalent call foo(valueParam, capturedParam1, cp2 ...).
 But lowered closure for lambda parameter has totally different parameters order:

     fun loweredLambda$x(extensionReceiver, captured1, cp2..., valueParam1, vp2...)

 So before inlining lowered closure should be transformed to

     fun loweredLambda$x(extensionReceiver, valueParam1, vp2..., captured1, cp2..)

 #KT-28547 Fixed

2019-01-03 07:57:36 +01:00

..

defaultParam.kt

Proper resort variables on inlining lowered ir closures

2019-01-03 07:57:36 +01:00

lambdaInLambdaCapturesAnotherFun.kt

Unmute ir-tests after CR support

2018-08-09 14:22:50 +03:00

localFunInLambda.kt

Proper resort variables on inlining lowered ir closures

2019-01-03 07:57:36 +01:00

localFunInLambdaCapturesAnotherFun.kt

Unmute jvm-ir inline tests

2018-08-02 13:19:24 +02:00