Cheng Shao

Additional notes: * We'll likely need to evaluate the influence of different link-time options (e.g. enabling tail calls, yolo mode, different gc thresholds), since they can have a significant impact...

This is clearly an OOM condition. The CircleCI medium resource class has 4GB memory, which unfortunately may be not enough when linking some large executables. We're aware of the excessive...

Hi, we don't have support for `stack` yet; you can try `ahc-cabal` which is a wrapper for `cabal` to build cabal projects.

We don't support REPL yet.

Major WASI reference list: [WASI Core API](https://github.com/bytecodealliance/wasmtime/blob/master/docs/WASI-api.md) [WASI Constants](https://github.com/bytecodealliance/wasmtime/blob/master/crates/wasi-c/src/wasm32.rs)

Since the WASI Core API depends on passing `i64` across js/wasm boundary, this issue and #407 is blocked by #33. Better implement a uniform i64 FFI mechanism and clean up...

The WASI API documentation doesn't seem to match the implementation. I eyeballed the `wasm-objdump` of a "typical" wasi binary from https://wapm.io/package/lucklove/tidb#explore, and the `wasi_unstable` import function signatures don't match the...

See https://github.com/WebAssembly/WASI/issues/54 for upstream discussion of `i64` FFI problem The status quo seems to be: * For non-web engines like `wasmer` or `wasmtime`, `i64` can appear in a `wasi` import...

I agree that a bazel-based build system could address some of the points listed above. I'm conservative about whether it'll help the CI story though. It may cache the build...

Thanks for reporting. I have a WIP branch for fixing & testing darwin support [here](https://github.com/tweag/asterius/tree/wip-darwin-ci); after fixing the `@` issue of booting, it now [fails](https://circleci.com/gh/tweag/asterius/7640) with the following error message...