Luke Wagner

Would a good next step be to write up a more-complete `world.md` in the style of the current `wit.md`?

If we're talking about shared-memory parallelism for wasi-parallel (my suggestion in [wasi-parallel/#3](https://github.com/WebAssembly/wasi-parallel/issues/3) was thinking more about *non*-shared-memory parallelism), I think a good way to express this in a way that...

I might be misunderstanding, but it seems like if wasi-parallel offers shared-memory-multi-threading, `wit-bindgen` doesn't have anything to offer since you don't want to copy data between linear memories (there is...

Well, my hypothesis is that: when doing memory sharing, you don't need/want `wit-bindgen`; you're passing around `i32` pointers through interfaces and you want it that way. So I don't understand...

Oh, sorry, maybe I'm misunderstanding the fundamental interface here. When I heard "caller's memory", I assumed that was because the interfaces were passing pointers (offsets) relative to a linear memory...

Ah, that helps, thanks. Could you describe in a bit more detail how you're imagining to declare the memory that the callback needs and how it gets passed to/from the...

If there's a need for a lightweight, portable, language-agnostic sandbox, wasm sounds like a good fit :) I don't have enough context or knowledge of Solid to know what the...

@Mossaka Here's a first stab at an answer but maybe we should move any follow-up discussion to a new issue so we can dig in. If I understand your scenario...

Could we allow world imports and exports to have inline function (and later potentially other) types, e.g.: ```wit world my-world { import fs: "wasi:filesystem" import foo: func(x: string) -> string...

Oh, sorry, I misunderstood. I would guess "no" and if we decide we need it in the future, it would be some new keyword specifically for "splatting" interfaces.