<https://gist.github.com/Bompedy/b8a935dcbd28eef57...

# compiler

[Exerosis]

https://gist.github.com/Bompedy/b8a935dcbd28eef5727416e4b5a90c39#file-main-kt
Anyone know what's going on with context receivers in JS?
They like sort of work but I'm getting:

Uncaught TypeError: $context_receiver_0 is not a function
    at invoke_15 (Toggled.kt:17:7)
    at protoOf.doResume_5yljmg_k$ (Main.kt:15:9)
    at protoOf.invoke_3gufz3_k$ (Main.kt:14:9)
    at $ComponentCOROUTINE$7.l [as block_1] (godtier.js:7721:16)
    at protoOf.doResume_5yljmg_k$ (Toggled.kt:184:27)
    at Component_0 (Toggled.kt:184:7)
    at protoOf.doResume_5yljmg_k$ (Main.kt:13:21)
    at main (Main.kt:9:20)
    at mainWrapper (godtier.js:7772:5)
    at Object.eval (godtier.js:19965:3)

Sorry to send such a complex block of code it's adapted from something we had working just fine on JVM. (although it has historically at times been too complicated for kotlin compiler to handle even on JVM so IG I'm not exactly the most shocked but might be good to have someone start investigation)
I think maybe it's suspend + context

[Pavel Kunyavskiy [JB]]

They can work in simple cases by accident, but it was never tested for non-jvm backends. Note, that context receivers are on the road of being replaced by context parameters, which would work on all backends, when they would be ready.

[Exerosis]

This is a tragic set of changes (at least for me) in my opinion, is there a thread that explains the reasoning/history behind these decisions and or I good place to provide feedback?