You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dashmap uses the sync_guard feature of parking_lot. However, in my codebase, I use parking_lot throughout, and I intentionally want parking_lot guards to not be Sync, as defense against accidentally keeping them across .await points (which can easily lead to deadlocks).
But I cannot do so unless I downgrade dashmap to v4, because dashmap will turn on the sync_guard feature for me. This has caused several accidental deadlocks in my code already.
Can this be controlled at least by a feature flag? I don't want dashmap Refs to be Sync either.
The text was updated successfully, but these errors were encountered:
deftsp
added a commit
to deftsp/dashmap
that referenced
this issue
Jan 26, 2022
dashmap
uses thesync_guard
feature of parking_lot. However, in my codebase, I use parking_lot throughout, and I intentionally want parking_lot guards to not be Sync, as defense against accidentally keeping them across.await
points (which can easily lead to deadlocks).But I cannot do so unless I downgrade dashmap to v4, because dashmap will turn on the
sync_guard
feature for me. This has caused several accidental deadlocks in my code already.Can this be controlled at least by a feature flag? I don't want dashmap Refs to be Sync either.
The text was updated successfully, but these errors were encountered: