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.
-
-
Basically building abstractions where sync/send meant something more specific (representing the main vs interrupt split), because we didn't have "threads". Then expanding that definition to be sync or send across cores. May not be directly equivalent, but somewhat similar?
-
Ah, I think this is different! In our case we don't have threads in the browser yet, which means we can take the adherence to Send/Sync. Once we have threads tho we should use a parked thread instead to actually implement it correctly.
End of conversation
New conversation -
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.