Zalim Bashorov

@little-willy Hi! Thanks for the message. Binary files are the source for true in our case :). I've looked at the error from the reference interpreter, and it looks like...

We can provide a custom build that traps (unreachable) instead of throwing. If KoWasm and its dependencies don't use exceptions for positive scenarios, it should be enough for experimenting. Please...

@alabulei1 @juntao, is there a plan/ETA for exception handling support in WasmEdge?

> We cannot directly link functions defined in JavaScript, so we can only supplement these host functions through APIs/plugins @L-jasmine @juntao do you have any plan about supporting it? Just...

@lppedd is right, `-libraries` should be what you need.

> It's not mentioned anywhere and it's what made me rethink my life in the last hour (joking, almost), but -ir-output-dir must be absolute. God's know where my hundreds of...

It looks like a one-step compilation for K/Wasm is broken in K2. You can for compiler work as K1 like below and it should work: ```shell kotlinc-js -language-version 1.9 -Xir-produce-js...

For K2 you need to do two steps: ### 1: Produce a klib for sources ```shell kotlinc-js -Xwasm -Xwasm-target=wasm-js -Xir-produce-klib-dir -no-stdlib -libraries kotlin-stdlib-wasm-js-2.0.0-Beta3.klib -ir-output-name mymodule -ir-output-dir mymodule-klib -Xir-per-module-output-name=mymodule Simple.kt ```...

> Notice there is no test-klib and no test-module being generated by the first pass... What is `test-klib` and `test-module`? That you see on the picture is an unpacked klib...

I wouldn't add git submodules; they are used to be painful. I think it would be enough and simple: 1. Change links from root Readme.md 2. Keep in folders only...