> >> *Web developers*: No signals >> > > Have you tried to gather signals? Are there developers involved in the > WASM process? (if so, the phase can count as a signal for them as well). >
Maybe Leaning Tech qualifies: they develop an x86 virtualization technology using wasm. They have written publicly about their use case for tail calls ( here <https://leaningtech.com/extreme-webassembly-2-the-sad-state-of-webassembly-tail-calls/>, here <https://github.com/WebAssembly/tail-call/issues/12> and here <https://leaningtech.com/fantastic-tail-calls-and-how-to-implement-them/>), and unblocked the move to phase 4 by implementing it in WebKit (here <https://github.com/WebKit/WebKit/pull/2065>). >> *Other signals*: >> >> WebView application risks >> >> Does this intent deprecate or change behavior of existing APIs, such that >> it has potentially high risk for Android WebView-based applications? >> > > I'm guessing the answer here is "no"? > Indeed. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALowwNYfhC78Juo%3DBg%2Bp8OD77A4%3Dha7nU%2BCcXFe58R%3DX%2BmrUHA%40mail.gmail.com.
