use LazyLock instead of lazy_static!
#454
Merged
Conversation
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
moritz-gross
changed the title
LazyLock in prefs.rsLazyLock instead of lazy_static!
Collaborator
|
Good catch. I didn't know that |
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.
from my research, the functionality of
lazy_static!has moved into the core library of the Rust language withLazyLock.once this is simplified in the other files, the crate
lazy_staticcould be removed.I have not change all spots where this would apply.
I'm a bit disappointed in whatever diff implementation GitHub uses, I re-checked that none of the Regex's are touched, but here it only highlights the whole line and no individual language parts.