refactor: replace OnceLock with LazyLock#14880
Merged
alamb merged 1 commit intoapache:mainfrom Feb 25, 2025
Merged
Conversation
this commit replaces all the remaining references of OnceLock with LazyLock
github-actions
bot
added
logical-expr
alamb
approved these changes
Feb 25, 2025
Contributor
alamb
left a comment
alamb
left a comment
There was a problem hiding this comment.
Thank you @AmosAidoo
cc @comphead
Contributor
|
This PR turns out to have gotten the 10,000th commit:
😮 |
Contributor
Author
|
😮 So proud |
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.
Which issue does this PR close?
OnceLockwithLazyLock#11687.Rationale for this change
LazyLock is more ergonomic than OnceLock.
What changes are included in this PR?
Replaces the remaining references of OnceLock in the codebase with their LazyLock equivalents.
Are these changes tested?
Yes, by existing tests.
Are there any user-facing changes?