Kotlin 2.0 and Nullability Annotations
New and Enhanced Features
-
Upgraded to Kotlin 2.0.0
-
Upgraded to JUnit Platform 1.10.3
Breaking Changes
-
StatisticsCoverage.checkQuery(Predicate<? super List<?>> query)
:
query
is now of typePredicate<? super List<?>>
instead ofPredicate<? super List<Object>>
. -
Nullability annotations have been added to many API methods and interfaces.
This could lead to compile-time warnings or errors in your code if you are using tool chains that validate those. -
UniqueElements.by()
now requires aClass<? extends Function<? extends @Nullable Object, ?>>
instead of aClass<? extends Function<?, Object>>
.
Bug Fixes
-
Tools like CheckerFramework did not play well with jqwik's (wrong) usage of
@Nullable
on type variables.
This has been fixed. See issue 575 for details.
Thanks to vlsi for working out all the nitty, gritty details! -
Fixed type matching bug as revealed in this comment