7d59c7689c
JVM IR: Avoid direct invokes in callable reference tests
...
Due to the direct invoke optimization, most callable reference tests
were not generating callable references/lambdas.
2022-07-14 23:24:18 +02:00
41a69ad388
[WASM] Add receiver capturing to callable references
2021-09-20 19:08:22 +03:00
fdd7fa5aea
[Wasm] Mute codegen box tests
2020-11-09 16:04:43 +03:00
282509b0da
[FIR2IR] Provide object receivers for callable references
2020-03-31 20:27:24 +03:00
9df2f69f09
[FIR] Disable failing blackbox codegen tests for FIR.
2019-11-19 11:00:09 +03:00
357359b1dd
Unmute ir-tests after CR support
2018-08-09 14:22:50 +03:00
e149cbe852
Mute failed jvm ir tests
2018-06-28 12:26:41 +02:00
159df7964a
JS: bound callable references (KT-13573).
2016-11-28 16:33:58 +03:00
3d2696c81b
KT-13440 Bound callable references in reflection
2016-11-25 16:11:18 +03:00
3dd0c9d1c7
Equality comparison for bound callable references takes into account bound receiver.
...
Fixed KT-14939: use expected receiver type when generating receiver code in get/set methods for bound property references.
Otherwise we have VerifyError for bound receiver 'null' of type 'Nothing?', which is mapped to 'java.lang.Void'.
TODO: proper equality comparison for property accessors ('x::prop.getter', 'x::prop.setter').
2016-11-25 14:49:24 +03:00
Steven Schäfer