I think the answer is to do an unsafe impl of a Send bound around types that touch the DOM, because threads aren't available anyway, so the Send bound is meaningless in the browser right now anyway. Famous last words, probably.
Uh, so having Send bounds in WASM code around anything that might touch the DOM is not a great idea right now. Because JS refs can't be sent, and threads are generally unavailable (so we can't create a threadpool to park them). Things just took an unexpected turn.
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.