Luke Wagner

ooc, are these builds that run in a browser and, if so, what wasm interpreter are you using?

@yoshuawuyts The Rust code you wrote makes sense, but one important thing to note is that, even without the hint set, in Preview 2 and beyond, the client of a...

Yes, sounds fine to me. Presumably this would actually be a `WebAssembly.CompileError` (or `WebAssembly.InternalError` if we decided on that). If we wanted to pull out bytecode offset or any other...

Looks like you already found it but, for the record, defaultable fields/params is discussed in #15. I think more discussion is needed on both of these and considering them simultaneously...

Since the core spec does have a defined notion of a custom section, I think it makes sense to give a fully-specified representation in the text format. While it's true...

> It probably isn't used much, but I would prefer not to break compatibility over it. In addition to text-format motivations, there's also the fact that if it's an infrequently...

I'm not sure if it's the exact same issue, but I had a specific fix that might help the situation here: https://bugzilla.mozilla.org/show_bug.cgi?id=1426124

The basic idea (described more [here](https://github.com/WebAssembly/component-model/blob/main/design/mvp/Explainer.md#import-and-export-definitions)) is that each import/export name has two parts, a developer-facing kebab-case string (meant to be converted into source-code bindings) and an optional `(id )`...

Returning to this with the benefit of seeing how everything else has developed in the meantime: a different way to think about creating a "CLI Embedding" is to consider Bash...

"Parametric linking" is a term that we've invented to describe the collection of features in the component-model that allow more-flexible, more-composable linking of components and modules. Specifically, I consider "parametric...