Skip to content
New issue

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

🔨 Death to raw mutex and lock usage #5172

Closed
3 tasks done
zach2good opened this issue Feb 20, 2024 · 1 comment
Closed
3 tasks done

🔨 Death to raw mutex and lock usage #5172

zach2good opened this issue Feb 20, 2024 · 1 comment
Assignees
Labels
enhancement New feature request

Comments

@zach2good
Copy link
Contributor

I affirm:

  • I understand that if I do not agree to the following points by completing the checkboxes my issue will be ignored.
  • I have read and understood the Contributing Guide and the Code of Conduct.
  • I have searched existing issues to see if the issue has already been opened, and I have checked the commit log to see if the issue has been resolved since my server was last updated.

Describe the feature

We have mutex_guarded and shared_guarded wrappers which do a much better job than managing this sort of thing by hand. We should be using them instead.

@zach2good zach2good added the enhancement New feature request label Feb 20, 2024
@zach2good zach2good self-assigned this Feb 20, 2024
@zach2good
Copy link
Contributor Author

This is the last place outside of common utils that uses raw locks/mutexes, so I'd consider this done: #6357

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature request
Projects
None yet
Development

No branches or pull requests

1 participant