WebAssembly/component-model#646 forbids the async canonopt with non-async functions. This makes the async opt to e.g. rust generate! look odd since "positive" overrides (like async: true) are always no-ops now (right?). "Negative" overrides are still meaningful but it seems like it would be less confusing for those to move to a new opt (!async: [...]? 🤷).
Regardless of what is done with the async opt in the long run it might make sense to start emitting warnings for positive overrides now, especially async: true.
Ref #1622
WebAssembly/component-model#646 forbids the async canonopt with non-async functions. This makes the
asyncopt to e.g. rustgenerate!look odd since "positive" overrides (likeasync: true) are always no-ops now (right?). "Negative" overrides are still meaningful but it seems like it would be less confusing for those to move to a new opt (!async: [...]? 🤷).Regardless of what is done with the
asyncopt in the long run it might make sense to start emitting warnings for positive overrides now, especiallyasync: true.Ref #1622