chore(deps): update dependency org.clojure/clojure to v1.12.0 #2046
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.
This PR contains the following updates:
1.11.4
->1.12.0
Release Notes
clojure/clojure (org.clojure/clojure)
v1.12.0
1 Compatibility
1.1 Java 8 - Compatiblity EOL notice
Clojure 1.12 produces Java 8 bytecode (same as Clojure 1.10 and 1.11), but this is expected to be the last release using a Java 8 baseline. Future releases will move the bytecode and minimum Java compatibility to a newer Java LTS release.
1.2 Java 21 - Virtual thread pinning from user code under
synchronized
Clojure users want to use virtual threads on JDK 21. Prior to 1.12, Clojure lazy-seqs and delays, in order to enforce run-once behavior, ran user code under synchronized blocks, which as of JDK 21 don't yet participate in cooperative blocking. Thus if that code did e.g. blocking I/O it would pin a real thread. JDK 21 may emit warnings for this when using
-Djdk.tracePinnedThreads=full
.To avoid this pinning, in 1.12
lazy-seq
anddelay
use locks instead of synchronized blocks.See: CLJ-2804
1.3 Security
Fix CVE-2024-22871 detailed in GHSA-vr64-r9qj-h27f:
iterate
,cycle
,repeat
- infinite seqs have infinitehashCode()
1.4 Serialization
CLJ-1327 explicitly sets the Java serialization identifier for the classes in Clojure that implement Java serialization. In Clojure 1.11.0 this changed for two classes unnecessarily and we reverted those changes in Clojure 1.11.1 - this completes that work for the rest of the classes.
Clojure data types have implemented the Java serialization interfaces since Clojure 1.0. Java serialization is designed to save graphs of Java instances into a byte stream. Every class has an identifier (the serialVersionUID) that is automatically generated based on the class name, it's type hierarchy, and the serialized fields. At deserialization time, deserialization can only occur when the available class has an identifier that matches the class id recorded in the serialized bytes.
Clojure has never provided a guarantee of serialization consistency across Clojure versions, but we do not wish to break compatibility any more than necessary and these changes will give us more control over that in the future.
See: CLJ-1327
1.5 Dependencies
Updated dependencies:
See: CLJ-2852
2 Features
2.1 Add libraries for interactive use
There are many development-time cases where it would be useful to add a library interactively without restarting the JVM - speculative evaluation, adding a known dependency to your project, or adding a library to accomplish a specific task.
Clojure now provides new functions to add libraries interactively, without restarting the JVM or losing the state of your work:
add-lib
, but resolves a set of new libraries and versions together.add-libs
with any libs present in deps.edn, but not yet present on the classpath.These new functions are intended only for development-time interactive use at the repl - using a deps.edn is still the proper way to build and maintain production code. To this end, these functions all check that *repl* is bound to true (that flag is bound automatically by
clojure.main/repl
). In a clojure.main REPL, these new functions are automatically referred in theuser
namespace. In other repls, you may need to(require '[clojure.repl.deps :refer :all])
before use.Library resolution and download are provided by tools.deps. However, you do not want to add tools.deps and its many dependencies to your project classpath during development, and thus we have also added a new api for invoking functions out of process via the Clojure CLI.
See: CLJ-2761, CLJ-2757, CLJ-2788, CLJ-2767, CLJ-2769, CLJ-2770
2.2 Invoke tool functions out of process
There are many useful tools you can use at development time, but which are not part of your project's actual dependencies. The Clojure CLI provides explicit support for tools with their own classpath, but there was not previously a way to invoke these interactively.
Clojure now includes clojure.tools.deps.interop/invoke-tool to invoke a tool function out of process. The classpath for the tool is defined in deps.edn and you do not need to add the tool's dependencies to your project classpath.
add-lib
functionality is built usinginvoke-tool
but you can also use it to build or invoke your own tools for interactive use. Find more about the function execution protocol on the CLI reference.See: CLJ-2760, CLJ-2819
2.3 Start and control external processes
For a long time, we've had the
clojure.java.shell
namespace, but over time Java has provided new APIs for process info, process control, and I/O redirection. This release adds a new namespace clojure.java.process that takes advantage of these APIs and is easier to use. See:See: CLJ-2759, CLJ-2777, CLJ-2828, CLJ-2773, CLJ-2776, CLJ-2774, CLJ-2778, CLJ-2779, CLJ-2865
2.4 Method values
Clojure programmers often want to use Java methods in higher-order functions (e.g. passing a Java method to
map
). Until now, programmers have had to manually wrap methods in functions. This is verbose, and might require manual hinting for overload disambiguation, or incur incidental reflection or boxing.Programmers can now use qualified methods as ordinary functions in value contexts - the compiler will automatically generate the wrapping function. The compiler will generate a reflective call when a qualified method does not resolve due to overloading. Developers can supply :param-tags metadata on qualified methods to specify the signature of a single desired method, 'resolving' it.
See: CLJ-2793, CLJ-2844, CLJ-2835
2.5 Qualified methods -
Class/method
,Class/.method
, andClass/new
Java members inherently exist in a class. For method values we need a way to explicitly specify the class of an instance method because there is no possibility for inference.
Qualified methods have value semantics when used in non-invocation positions:
Classname/method
- value is a Clojure function that invokes a static methodClassname/.method
- value is a Clojure function that invokes an instance methodClassname/new
- value is a Clojure function that invokes a constructorNote: developers must use
Classname/method
andClassname/.method
syntax to differentiate between static and instance methods.Qualified method invocations with param-tags use only the tags to resolve the method. Without param-tags they behave like the equivalent dot syntax, except the qualifying class takes precedence over hints of the target object, and over its runtime type when invoked via reflection.
Note: Static fields are values and should be referenced without parens unless they are intended as function calls, e.g
(System/out)
should beSystem/out
. Future Clojure releases will treat the field's value as something invokable and invoke it.See: CLJ-2844, CLJ-2848, CLJ-2847, CLJ-2853, CLJ-2867
2.6 :param-tags metadata
When used as values, qualified methods supply only the class and method name, and thus cannot resolve overloaded methods.
Developers can supply
:param-tags
metadata on qualified methods to specify the signature of a single desired method, 'resolving' it. The:param-tags
metadata is a vector of zero or more tags:[tag ...]
. A tag is any existing valid:tag
metadata value. Each tag corresponds to a parameter in the desired signature (arity should match the number of tags). Parameters with non-overloaded types can use the placeholder_
in lieu of the tag. When you supply :param-tags metadata on a qualified method, the metadata must allow the compiler to resolve it to a single method at compile time.A new metadata reader syntax
^[tag ...]
attaches:param-tags
metadata to member symbols, just as^tag
attaches:tag
metadata to a symbol.See: CLJ-2805
2.7 Array class syntax
Clojure supports symbols naming classes both as a value (for class object) and as a type hint, but has not provided syntax for array classes other than strings.
Developers can now refer to an array class using a symbol of the form
ComponentClass/#dimensions
, egString/2
refers to the class of a 2 dimensional array of Strings. Component classes can be fully-qualified classes, imported classes, or primitives. Array class syntax can be used as both type hints and values.Examples:
String/1
,java.lang.String/1
,long/2
.See: CLJ-2807
2.8 Functional interfaces
Java programs define "functions" with Java functional interfaces (marked with the @FunctionalInterface annotation), which have a single method.
Clojure developers can now invoke Java methods taking functional interfaces by passing functions with matching arity. The Clojure compiler implicitly converts Clojure functions to the required functional interface by constructing a lambda adapter. You can explicitly coerce a Clojure function to a functional interface by hinting the binding name in a
let
binding, e.g. to avoid repeated adapter construction in a loop, e.g.(let [^java.util.function.Predicate p even?] ...)
.See: CLJ-2799, CLJ-2858, CLJ-2856, CLJ-2863, CLJ-2864
2.9 Java Supplier interop
Calling methods that take a Supplier (a method that supplies a value) had required writing an adapter with reify. Clojure has a "value supplier" interface with semantic support already -
IDeref
. AllIDeref
impls (delay
,future
,atom
, etc) now implement theSupplier
interface directly.See: CLJ-2792, CLJ-2841
2.10 Streams with seq, into, reduce, and transduce support
Java APIs increasingly return Streams and are hard to consume because they do not implement interfaces that Clojure already supports, and hard to interop with because Clojure doesn't directly implement Java functional interfaces.
In addition to functional interface support, Clojure now provides these functions to interoperate with streams in an idiomatic manner, all functions behave analogously to their Clojure counterparts:
(stream-seq! stream) => seq
(stream-reduce! f [init-val] stream) => val
(stream-transduce! xf f [init-val] stream) => val
(stream-into! to-coll [xf] stream) => to-coll
All of these operations are terminal stream operations (they consume the stream).
See: CLJ-2775
2.11 PersistentVector implements Spliterable
Java collections implement streams via "spliterators", iterators that can be split for faster parallel traversal.
PersistentVector
now provides a custom spliterator that supports parallelism, with greatly improved performance.See: CLJ-2791
2.12 Efficient drop and partition for persistent or algorithmic collections
Partitioning of a collection uses a series of takes (to build a partition) and drops (to skip past that partition). CLJ-2713 adds a new internal interface (IDrop) indicating that a collection can drop more efficiently than sequential traversal, and implements that for persistent collections and algorithmic collections like
range
andrepeat
. These optimizations are used indrop
,nthrest
, andnthnext
.Additionally, there are new functions
partitionv
,partitionv-all
, andsplitv-at
that are more efficient than their existing counterparts and produce vector partitions instead of realized seq partitions.See: CLJ-2713, CLJ-2742, CLJ-2740, CLJ-2715, CLJ-2718, CLJ-2772, CLJ-2741
2.13 Var interning policy
Interning a var in a namespace (vs aliasing) must create a stable reference that is never displaced, so that all references to an interned var get the same object. There were some cases where interned vars could get displaced and those have been tightened up in 1.12.0-alpha1. If you encounter this situation, you'll see a warning like "REJECTED: attempt to replace interned var #'some-ns/foo with #'other-ns/foo in some-ns, you must ns-unmap first".
This addresses the root cause of an issue encountered with Clojure 1.11.0, which added new functions to clojure.core (particularly
abs
). Compiled code from an earlier version of Clojure with var names that matched the newly added functions in clojure.core would be unbound when loaded in a 1.11.0 runtime. In addition to CLJ-2711, we rolled back a previous fix in this area (CLJ-1604).See: CLJ-2711
3 Fixes and enhancements
3.1 Reader and Compiler
#uuid
data reader - Fix exception on invalid input so it flows through reader^:once
fnsrecur
to head of:once
fn cancels once3.2 Core
range
- Use optimized range for int argsrange
- Fix invalid arg order when adding meta to non-optimized rangewith-open
- Fix to not qualify.close
method on expansionclojure.java.io/do-copy
- Fix incorrect type hintex-info
- now handles nil data mapnthrest
now returns rest output on n=0 or past end of seqempty?
- adds support forcounted?
collectionsclojure.walk/walk
- preserve metadata on lists and seqsclojure.core.server/parse-props
- Fix exception if system properties concurrently modified during initializationPrintWriter-on
should support auto-flush, and prepl should use it for the err streamdefprotocol
- ignore unused primitive return type hints3.3 Docstrings
assert
and\*assert*
- improve docstrings to add contextinto
- add 0- and 1-arity to docstringreify
- improve docstring and fix exampletransient
- include usage model from reference docsConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.