I think it might be worthwhile to use WASI for the RTS instead of the transliteration from the C RTS in CMSC430.
I still have more to investigate, but I think that long-term this will benefit the project as it will allow you to use alternative wasm engines (such as wasmtime for running natively).
The engineer that wrote the WASI API for wastime is willing to help me learn the ropes, so hopefully I'm able to do it.
I should probably make a separate issue for it, but what's the "ideal" use case for wacket? Writing web-app frontends in racket? If so it probably matters less that WASI is used (though there are probably still bit performance benefits as it's reduces the impedance mismatch.
I think it might be worthwhile to use WASI for the RTS instead of the transliteration from the C RTS in CMSC430.
I still have more to investigate, but I think that long-term this will benefit the project as it will allow you to use alternative wasm engines (such as wasmtime for running natively).
The engineer that wrote the WASI API for wastime is willing to help me learn the ropes, so hopefully I'm able to do it.
I should probably make a separate issue for it, but what's the "ideal" use case for wacket? Writing web-app frontends in racket? If so it probably matters less that WASI is used (though there are probably still bit performance benefits as it's reduces the impedance mismatch.