yonihemi

Thanks for reviewing this! Async/await is exciting but its implementation in SwiftWasm might not be related or solve the exact same issue this is solving. Let's take this code snippet...

There is a bug with processing incoming events while suspended. Let me push a fix, though not before tomorrow. Even so, I'm not sure about merging this. I have some...

Made a [working sample](https://github.com/yonihemi/AsyncifySample).

Looks like I haven't managed to present the case for Asyncify successfully. Not surprising, as this was the fate of similar patches in most projects except Emscripten itself. It's a...

I think the changes in #369 are required so the Reactor Model changes stick in compiler versions >= 5.6? Guess it was lost by closing the other PR without merging.

To have carton pick up the toolchain, you'll need to have a `.swift-version` file at the root of the project with the name, e.g. `wasm-5.4-SNAPSHOT-2021-07-25-a`. You can then verify this...

This one is super annoying, though I suspect for now must users just tinker around with Tokamak. Problem is TSC's FSWatch is not geared towards individual files but entire folders....

I think the issue comes from our use of libSwiftPM - on macOS it defaults to use the toolchain provided by xcrun vs our toolchain. We have an [imminent fix](https://github.com/swiftwasm/carton/pull/381)...

Thanks for reporting @gmondada. I'm looking into it, seems to be swift driver misinterpreting an argument passed from SwiftPM when building. I wonder if it's just an issue that crept...

`not worth using even if it compiles` is highly subjective, and is not the correct tradeoff for every project. For example, for several years before ABI stability was introduced on...