We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On mac, windows, and linux, the proxy type has an unsafe impl so the proxy can be shared across threads
pub struct Proxy<T> { sender: Sender<T>, source: CFRunLoopSourceRef, } unsafe impl<T: Send> Send for Proxy<T> {} unsafe impl<T: Send> Sync for Proxy<T> {}
But this does not exist for iOS.
I have to hack around this limitation by doing these impls myself. It'd be great if this was just built in.
The text was updated successfully, but these errors were encountered:
I think it is probably safe to implement Sync for it but I am not sure since I can't test it, however, Send is implemented for the proxy on iOS
Sync
Send
tao/src/platform_impl/ios/event_loop.rs
Lines 164 to 169 in b3aa398
Shouldn't that be enough? like you can create a new proxy and just send it to the thread instead of sending a reference.
Sorry, something went wrong.
EventLoopProxy
T
Successfully merging a pull request may close this issue.
On mac, windows, and linux, the proxy type has an unsafe impl so the proxy can be shared across threads
But this does not exist for iOS.
I have to hack around this limitation by doing these impls myself. It'd be great if this was just built in.
The text was updated successfully, but these errors were encountered: