Release 3.23.0 of the Checker Framework
10 views
Skip to first unread message
Michael Ernst
Jul 11, 2022, 7:33:47 PM7/11/22
to checker-fram...@googlegroups.com
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.23.0:
User-visible changes:
By default, command-line argument `-AstubWarnIfNotFound` is treated as true for stub files provided on the command line and false for built-in stub files. Use `-AstubWarnIfNotFound` to enable it for all stub files, and use new `-AstubNoWarnIfNotFound` to disable it for all stub files.
New command-line argument `-ApermitStaticOwning` suppresses Resource Leak Checker warnings related to static owning fields.
New command-line argument `-ApermitInitializationLeak` suppresses Resource Leak Checker warnings related to field initialization.
Closed issues:
#4855, #5151, #5166, #5172, #5175, #5181, #5189.
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.23.0:
User-visible changes:
By default, command-line argument `-AstubWarnIfNotFound` is treated as true for stub files provided on the command line and false for built-in stub files. Use `-AstubWarnIfNotFound` to enable it for all stub files, and use new `-AstubNoWarnIfNotFound` to disable it for all stub files.
New command-line argument `-ApermitStaticOwning` suppresses Resource Leak Checker warnings related to static owning fields.
New command-line argument `-ApermitInitializationLeak` suppresses Resource Leak Checker warnings related to field initialization.
Closed issues:
#4855, #5151, #5166, #5172, #5175, #5181, #5189.
Reply all
Reply to author
Forward
0 new messages