daxpedda
daxpedda
I forgot to mention that there is a way to get rid of the `exception-handling` guard. We can add unwind-safety the same way Std does: by just adding a struct...
~~I thought we discussed this in the last meeting and concluded that we won't do this? Or what are you planning to do in this PR?~~ EDIT: apologies! Just saw...
With incorrect I meant UB here. > An android-activity app is given a main thread that is conceptually subordinate to the Java thread and needs to be able to gracefully...
> Are there other use-cases for `Send + Sync` windows (other than rendering)? It is still highly desirable for MT applications to be able to call all sort of `Window`...
That seems sensible to me, I'm happy to review a PR.
This was done as part of #370.
> I believe that we should make `set_cursor_position` and the pointer APIs use surface coordinates, since that's the easier coordinate system for users to work with. Agreed. This is already...
I'm not aware of the historic context here, but this has been working as long as I have known `wasm-bindgen`. You can continue relying on it as it won't stop...
> the issue seems to be that in Wasm, user events don't interrupt when the event loop is waiting Let me know if this is a Winit bug, last time...
I'm happy to review a PR making the `std` feature no-op.