Upgrade Checker Framework Annotations 3.48.4 -> 3.49.0 #1537
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:
3.48.4
->3.49.0
Release Notes
typetools/checker-framework (Checker Framework Annotations)
v3.49.0
: Checker Framework 3.49.0Version 3.49.0 (February 3, 2025)
User-visible changes:
The Optional Checker is more precise for
Optional
values resulting fromoperations on container types (e.g.,
List
,Map
,Iterable
). It supportstwo new annotations:
@NonEmpty
@UnknownNonEmpty
The Signature Checker no longer supports
@BinaryNameWithoutPackage
becauseit is equivalent to
@Identifier
; use@Identifier
instead.The JavaStubifier implementation now appears in package
org.checkerframework.framework.stubifier.JavaStubifier
.Closed issues:
#6935, #6936, #6939.