sunfish added a comment. In D150803#4401204 <https://reviews.llvm.org/D150803#4401204>, @sbc100 wrote:
> In D150803#4401061 <https://reviews.llvm.org/D150803#4401061>, @sunfish wrote: > >> wasm_jspi works for me. > > The problem with that is that we will also likely want to use this attribute > for asyncify (which is the current async approach we have today) as well as > JSPI (which is hopefully coming soon) Ah, I see. Would it be accurate to say that asyncify is acting as a kind of a polyfill for JSPI in this situation, such that `wasm_jspi` is actually correct? Alternatively, what would you think about `wasm_external_async`? Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D150803/new/ https://reviews.llvm.org/D150803 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
