Yan
Yan
I'm experimenting to see how far we can go without any control flow :) For your use case, we can refactor the script into three separate files: 1) creating canisters;...
Any update on this PR?
I also have a use case which requires non-first-`word` to start with numbers. I need to auto-generate a interface with all resources from a world. For example, ``` use wasi:io/[email protected].{input-stream};...
Yes, it's still a PR. Will ping back when it's ready to merge.
> Rust assumes memory 0, so you wouldn't be able to just write the adapter in Rust code as we currently do unless we do a lot of toolchain work...
> I think it'd be relatively reasonable to as it's a somewhat-simple hash/equality function of a type. That's an interesting idea! So we need to look for structural equality for...
Interesting project! I was wondering have you tried to use the Rust analyzer for static analysis. Their libraries are all on crates-io, e.g., https://docs.rs/ra_ap_hir/latest/ra_ap_hir/, so no nightly rustc is required....
> The adapter module shouldn't have anything to shift, though, so I'm assuming you mean the main module? The problem with that would be that linear memory addresses are baked...
> Effectively you'd probably also have to update all memory.grow instructions as well. Yes, we subtract 2 pages from `memory.grow` and `memory.size`. We also add 2 pages to the initial...
> if the main concern is only preexisting modules Yes, it's only for preexisting WASI p1 modules. If the upstream language already supports component model, we wouldn't need to run...