Guy Bedford

Thanks for the feedback, I hadn't thought of the cross-over so that's very interesting to consider. I do wonder if loader customization could be seen to be a fully orthogonal...

Thanks for putting thought to these variations. Yes, where we currently do `import WasmModule from 'wasm-module'; WebAssembly.instantiate(...)` that is effectively doing parameterization but moving all the parameters to dynamic JS....

@sebmarkbage you mention the preloading use case as a goal of the asset references proposal: > What I really want is `preload('specifier').then(module => execute(module).thisIsSynchronouslyAvailable);` This may be better achieved through...

@sebmarkbage to clarify, both Luca and I actually support the principle of the asset references proposal even as a possible import reflection as described in this issue. The reference use...

Thanks for the summary here @lucacasonato, that sounds very clear to me and a really elegant separation of concerns. To try rephrase in ECMA-262 terms: * `HostResolveImportedModule` is split up...

Sorry, on second thoughts I think `"asset"` is actually exactly the right terms since that does seem to adequately capture a file or network asset, as long as we are...

@devongovett I wonder if a usecase like preload might not be better suited to a dedicated `import.preload` function in due course over attributes. Are there specific reasons you'd want attributes...

`` is the early hint for browsers, and is preferable to discovered preloads (which involves latency) for the static case.

> Sure, for initial page loads but would be nice to have a way to preload things for later loaded things other than insert one of those into the document...

Thanks @littledan for clarifying here, we are open to using an alternative syntax to `as` and would like to explore these options further, in a way that can work with...