Guy Bedford

Took a brief look at this today, didn't have time for a full review again but some initial thoughts: > We also know that sj is not reachable from Next(sj-1),...

Thinking about this some more... the important point is that per your first counter example case, because we skip over modules already linked, any reaching back to formerly visited graphs...

To clarify - I mean in the combined cycle cases where both cycles in your images appear. Another interesting cycle case is when successive direct dependencies each import a higher...

Cross-posting @lukewagner's comment from https://github.com/WebAssembly/esm-integration/pull/115: > Just my 2c on wasm: vs wasm-js:: although longer, wasm-js is attractive since it makes it clear from both a JS/ESM and wasm perspective...

I have been tentatively considering using `wasm-js:` here for things which are "JS conventions" and not actually even builtins. That is - in the (unlanded) phase integration proposal (https://github.com/WebAssembly/esm-integration/pull/117) I...

Sure, agreed with aligning on `wasm:` here then and avoiding `wasm-js:` for now. Let's please ensure `wasm:js/string-constants` is an exception to most other builtins though in using a kebab name,...

@eqrion thanks for taking a look here. I wonder if compact imports could be framed as an optimization that would result in a single instance import like `("wasm-js:strings" "*")` then...

> However the Vec and JsValue downcasting are not supported yet. It might be possible to support this case by implementing the corresponding ABI support for exported structs.

Sorry, correction - it wouldn't apply to exported arguments due to the ownership model. The fix might actually be to define this as an imported struct, so that it can...

I still can't find any usage examples of this hostcall in other SDKs, putting on hold for now.