Open
Conversation
frenchy64
force-pushed
the
require-lock
branch
from
a27bad1 to
a5de958
Compare
Member
|
The warning isn't a big deal either way, but I did look into the popularity of older Clojure versions, and 1.10 was already being phased out in 2022: https://clojure.org/news/2024/12/02/state-of-clojure-2024. |
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.
Ensures we don't race with other requiring threads.
Note this is now safer than
requiring-resolve(as of Clojure 1.12), which has a race condition making it prone to returning a partially initialized var.