Remove lazily initialized Mutex - #723
Merged
workingjubilee merged 1 commit intoSep 23, 2025
Merged
Conversation
Mutex::new is const since 1.63, which is below the 1.82 MSRV, so this should be fine to rely on.
Member
Author
|
(CI failure looks like a bug in GitHub probably?) |
Member
Author
|
Alright, that fixed CI. Should be ready for review. |
Member
|
Thanks! |
workingjubilee
approved these changes
Sep 23, 2025
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mutex::new is const since 1.63, which is below the 1.82 MSRV, so this should be fine to rely on. I wouldn't expect this to practically matter ~ever, but spotted this while poking around and it seems like a nice bit of cleanup (also removes a bit of unsafe and a leaked allocation).