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
Hi. Do you think we could remove the dependency to parking_lot now that std's Mutex is faster than before? Regards.
The text was updated successfully, but these errors were encountered:
Why?
parking_lot also avoids the poisoning behavior.
Sorry, something went wrong.
Oh, I thought it was used for performance reasons. So, removing it would reduce the build time.
But if it was used to avoid this behavior, then I guess there's no reason to remove it.
You can get same behaviour by simple wrapper:
struct Mutex<T>(std::sync::Mutex<T>); impl<T> Mutex<T> { pub fn lock(&self) -> std::sync::MutexGuard<T> { self.0.lock().unwrap_or_else(PoisonError::into_inner) } }
Successfully merging a pull request may close this issue.
Hi.
Do you think we could remove the dependency to parking_lot now that std's Mutex is faster than before?
Regards.
The text was updated successfully, but these errors were encountered: