Bump checker-qual from 3.11.0 to 3.13.0

[dependabot]

Bumps checker-qual from 3.11.0 to 3.13.0.

Release notes

Sourced from checker-qual's releases.

Checker Framework 3.13.0

Version 3.13.0 (May 3, 2021)

Survey:

If you use the Checker Framework, please answer a 3-question survey about what version of Java you use. It will take less than 1 minute to complete. Please answer it at https://docs.google.com/forms/d/1Bbt34c_3nDItHsBnmEfumoyrR-Zxhvo3VTHucXwfMcQ . Thanks!

User-visible changes:

Command-line argument -AassumeKeyFor makes the Nullness Checker and Map Key Checker unsoundly assume that the argument to Map.get is a key for the receiver map.

Warning message keys are shorter. This reduces clutter in error messages and in @SuppressWarnings annotations. Most ".type.invalid", ".type.incompatible", ".invalid", and ".not.satisfied" suffixes and "type.invalid." prefixes have been removed, and most ".invalid." substrings have been changed to ".".

The Checker Framework no longer crashes on code that contains binding variables (introduced in Java 14 for instanceof pattern matching), and such variables are reflected in the control flow graph (CFG). Thanks to Chris Day for this change. However, note that the Checker Framework only has full support for Java 8 and Java 11.

New command-line argument -AstubWarnNote makes stub file warnings notes rather than warnings.

Removed the StubGenerator section from the manual, because changes in JDK 11 have broken the StubGenerator program.

Implementation details:

Method renamings:

• DependentTypesHelper.atReturnType => atMethodBody

Closed issues: #1268, #3039, #4410, #4550, #4558, #4563, #4566, #4567, #4571, #4584, #4591, #4594, #4600.

Checker Framework 3.12.0

Version 3.12.0, April 1, 2021

User-visible changes:

New FAQ item "How should I annotate code that uses generics?" gives examples of annotations on type variables, together with their meaning.

-Ainfer=ajava uses ajava files (rather than jaif files or stub files) internally during whole-program inference.

The Optional Checker supports a new annotation @OptionalBottom that stands for (only) the null value.

The value element/argument to @EnumVal is now required. Previously it defaulted to an empty array.

Implementation details:

A precondition or normal postcondition annotation's value element must have type String[], not String. A conditinoal postcondition annotation's expression element must have type String[], not String. These changes will not affect users (any programmer-written annotation that was legal before will still be legal), but it may affect checker implementations.

JavaExpressionParseUtil: JavaExpressionParseUtil#parse no longer viewpoint-adapts Java expressions. It just converts the expression String to a JavaExpression. To that end, JavaExpressionParseUtil.JavaExpressionContext has been removed and JavaExpressionParseUtil#parse no longer takes a context object. Most calls to JavaExpressionParseUtil#parse should be replaced with a call to one of the methods in StringToJavaExpressions.

... (truncated)

Changelog

Sourced from checker-qual's changelog.

Version 3.13.0 (May 3, 2021)

Survey:

If you use the Checker Framework, please answer a 3-question survey about what version of Java you use. It will take less than 1 minute to complete. Please answer it at https://docs.google.com/forms/d/1Bbt34c_3nDItHsBnmEfumoyrR-Zxhvo3VTHucXwfMcQ . Thanks!

User-visible changes:

Command-line argument -AassumeKeyFor makes the Nullness Checker and Map Key Checker unsoundly assume that the argument to Map.get is a key for the receiver map.

Warning message keys are shorter. This reduces clutter in error messages and in @SuppressWarnings annotations. Most ".type.invalid", ".type.incompatible", ".invalid", and ".not.satisfied" suffixes and "type.invalid." prefixes have been removed, and most ".invalid." substrings have been changed to ".".

The Checker Framework no longer crashes on code that contains binding variables (introduced in Java 14 for instanceof pattern matching), and such variables are reflected in the control flow graph (CFG). Thanks to Chris Day for this change. However, note that the Checker Framework only has full support for Java 8 and Java 11.

New command-line argument -AstubWarnNote makes stub file warnings notes rather than warnings.

Removed the StubGenerator section from the manual, because changes in JDK 11 have broken the StubGenerator program.

Implementation details:

Method renamings:

• DependentTypesHelper.atReturnType => atMethodBody

Closed issues: #1268, #3039, #4410, #4550, #4558, #4563, #4566, #4567, #4571, #4584, #4591, #4594, #4600.

Version 3.12.0 (April 1, 2021)

User-visible changes:

New FAQ item "How should I annotate code that uses generics?" gives

... (truncated)

Commits

• 7d68bc2 new release 3.13.0
• a83d49e Merge branch 'master' of github.com:typetools/checker-framework
• c845981 Prep for 3.13.0 release.
• fd2a56f Add documentation about internal Gradle tasks that appear in Gradle output (#...
• 9a0e772 Documentation tweaks (#4620)
• 6eecc20 Mention the dataflow-shaded artifact (#4610)
• 4f7ba04 Bump classgraph from 4.8.104 to 4.8.105
• 662ccf5 Fix signature in reflection.astub
• a38dbdb Rename getAllAnnotations() to getImportedAnnotations()
• 79b4b4f Process stub files incrementally rather than making a list of them
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually