Release 3.32.0 of the Checker Framework
3 views
Skip to first unread message
Suzanne Millstein
Mar 2, 2023, 5:21:24 PM3/2/23
to Checker Framework discussion
We have released a new version of the Checker Framework.
The Checker Framework lets you create and/or run pluggable type checkers, in order to detect and prevent bugs in your code.
You can find documentation and download links at:
http://CheckerFramework.org/
Changes for Checker Framework version 3.32.0:
**User-visible changes:**
Fixed a bug in the Nullness Checker where a call to a side-effecting method did not make some formal parameters possibly-null. The Nullness Checker is likely to issue more warnings for your code. For ways to eliminate the new warnings, see https://checkerframework.org/manual/#type-refinement-side-effects .
If you supply the `-AinvocationPreservesArgumentNullness` command-line option, the Nullness Checker unsoundly assumes that arguments passed to non-null parameters in an invocation remain non-null after the invocation. This assumption is unsound in general, but it holds for most code.
**Implementation details:**
Moved `TreeUtils.isAutoGeneratedRecordMember(Element)` to `ElementUtils`.
Renamed `TreeUtils.instanceOfGetPattern()` to `TreeUtils.instanceOfTreeGetPattern()`.
Deprecated `AnnotatedTypes#isExplicitlySuperBounded` and `AnnotatedTypes#isExplicitlyExtendsBounded` because they are duplicates of `#hasExplicitSuperBound` and `#hasExplicitExtendsBound`.
The Checker Framework lets you create and/or run pluggable type checkers, in order to detect and prevent bugs in your code.
You can find documentation and download links at:
http://CheckerFramework.org/
Changes for Checker Framework version 3.32.0:
**User-visible changes:**
Fixed a bug in the Nullness Checker where a call to a side-effecting method did not make some formal parameters possibly-null. The Nullness Checker is likely to issue more warnings for your code. For ways to eliminate the new warnings, see https://checkerframework.org/manual/#type-refinement-side-effects .
If you supply the `-AinvocationPreservesArgumentNullness` command-line option, the Nullness Checker unsoundly assumes that arguments passed to non-null parameters in an invocation remain non-null after the invocation. This assumption is unsound in general, but it holds for most code.
**Implementation details:**
Moved `TreeUtils.isAutoGeneratedRecordMember(Element)` to `ElementUtils`.
Renamed `TreeUtils.instanceOfGetPattern()` to `TreeUtils.instanceOfTreeGetPattern()`.
Deprecated `AnnotatedTypes#isExplicitlySuperBounded` and `AnnotatedTypes#isExplicitlyExtendsBounded` because they are duplicates of `#hasExplicitSuperBound` and `#hasExplicitExtendsBound`.
Reply all
Reply to author
Forward
0 new messages