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
Is there any danger in assuming Send and Sync for types that contain windows_core::Weak? In comparison, std::sync::Weak is Send and Sync.
If it's safe, I'd like it to be implemented directly in the windows_core::Weak definition. Thanks!
The text was updated successfully, but these errors were encountered:
Send
Sync
Weak<T>
Yep, IWeakReference and IWeakReferenceSource are designed and implemented to be completely thread safe.
IWeakReference
IWeakReferenceSource
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Suggestion
Is there any danger in assuming Send and Sync for types that contain windows_core::Weak? In comparison, std::sync::Weak is Send and Sync.
If it's safe, I'd like it to be implemented directly in the windows_core::Weak definition. Thanks!
The text was updated successfully, but these errors were encountered: