Till Schneidereit

> Are there specific aspects of the API design where prototyping or analysis would be most helpful for moving the discussion forward? At this point I think the discussion is...

This relates to something we've talked about at various previous points: we should have semver checking tools for WIT. Those would be useful independently, but would also effectively avoid the...

@andreiltd is this different from the existing `builtins::web::dom_exception::DOMException::raise`?

> It might be nice for `func.new` to return a nullable reference (or whatever async equivalent) to signal this case, rather than raise a trap. > [..] > It also...

I think this might be possible using env vars, but I honestly don't know. I'm afraid I also don't have the time to dig into it, but if you find...

More generally speaking, the reasons for [specific proposals/features](https://docs.wasmtime.dev/stability-wasm-proposals.html) not being enabled by default in Wasmtime are all such that we absolutely shouldn't make different decisions in Spin: either the spec...

If we do anything with manifest flags, we should call them out as experimental, and make any attempt to publish the resulting app fail. And yes, we'd get requests to...

This is a very nice bikeshed; I'd like to contribute to it by arguing about the paint color! Where really all I'd suggest is to make this `--enable-unstable-features wasm_gc,wasm_reference_types,wasm_exceptions,wasm_function_references`

@itowlson thank you for the comments! I addressed the smaller ones in a new push as much as I could. I tried to make `new_application.supported = false` work, but the...

This always felt off to me as well, but I couldn't articulate why quite as clearly as laid out here—thank you for that! To enable adoption of the proposed format,...