Bump checker-qual from 3.6.1 to 3.7.0

[dependabot]

Bumps checker-qual from 3.6.1 to 3.7.0.

Release notes

Sourced from checker-qual's releases.

Checker Framework 3.7.0

Version 3.7.0, October 1, 2020

The new Called Methods Checker tracks methods that have definitely been called on an object. It automatically supports detecting mis-uses of the builder pattern in code that uses Lombok or AutoValue.

Accumulation analysis is now supported via a generic Accumulation Checker. An accumulation analysis is a restricted form of typestate analysis that does not require a precise alias analysis for soundness. The Called Methods Checker is an accumulation analysis.

The Nullness Checker supports annotations org.codehaus.commons.nullanalysis.NotNull, org.codehaus.commons.nullanalysis.Nullable, and org.jspecify.annotations.Nullable.

The Signature Checker supports annotations @CanonicalName and @CanonicalNameOrEmpty. The Signature Checker treats jdk.jfr.Unsigned as an alias for its own @Unsigned annotation.

The shorthand syntax for the -processor command-line argument applies to utility checkers, such as the Constant Value Checker.

Implementation details:

A checker implementation may override AnnotatedTypeFactory.getWidenedAnnotations to provide special behavior for primitive widening conversions.

Deprecated org.checkerframework.framework.util.MultiGraphQualifierHierarchy and org.checkerframework.framework.util.GraphQualifierHierarchy. Removed AnnotatedTypeFactory#createQualifierHierarchy(MultiGraphFactory) and AnnotatedTypeFactory#createQualifierHierarchyFactory. See Javadoc of MultiGraphQualifierHierarchy for instructions on how to use the new classes and methods.

Renamed methods: NumberUtils.isFloatingPoint => TypesUtils.isFloatingPoint NumberUtils.isIntegral => TypesUtils.isIntegralPrimitiveOrBoxed NumberUtils.isPrimitiveFloatingPoint => TypeKindUtils.isFloatingPoint NumberUtils.isPrimitiveIntegral => TypeKindUtils.isIntegral NumberUtils.unboxPrimitive => TypeKindUtils.primitiveOrBoxedToTypeKind TypeKindUtils.widenedNumericType => TypeKindUtils.widenedNumericType TypesUtils.isFloating => TypesUtils.isFloatingPrimitive TypesUtils.isIntegral => TypesUtils.isIntegralPrimitive

The CFStore copy constructor now takes only one argument.

Closed issues: #352, #354, #553, #722, #762, #2208, #2239, #3033, #3105, #3266, #3275, #3408, #3561, #3616, #3619, #3622, #3625, #3630, #3632, #3648, #3650, #3667, #3668, #3669, #3700, #3701.

Changelog

Sourced from checker-qual's changelog.

Version 3.7.0, October 1, 2020

The new Called Methods Checker tracks methods that have definitely been called on an object. It automatically supports detecting mis-uses of the builder pattern in code that uses Lombok or AutoValue.

Accumulation analysis is now supported via a generic Accumulation Checker. An accumulation analysis is a restricted form of typestate analysis that does not require a precise alias analysis for soundness. The Called Methods Checker is an accumulation analysis.

The Nullness Checker supports annotations org.codehaus.commons.nullanalysis.NotNull, org.codehaus.commons.nullanalysis.Nullable, and org.jspecify.annotations.Nullable.

The Signature Checker supports annotations @CanonicalName and @CanonicalNameOrEmpty. The Signature Checker treats jdk.jfr.Unsigned as an alias for its own @Unsigned annotation.

The shorthand syntax for the -processor command-line argument applies to utility checkers, such as the Constant Value Checker.

Implementation details:

A checker implementation may override AnnotatedTypeFactory.getWidenedAnnotations to provide special behavior for primitive widening conversions.

Deprecated org.checkerframework.framework.util.MultiGraphQualifierHierarchy and org.checkerframework.framework.util.GraphQualifierHierarchy. Removed AnnotatedTypeFactory#createQualifierHierarchy(MultiGraphFactory) and AnnotatedTypeFactory#createQualifierHierarchyFactory. See Javadoc of MultiGraphQualifierHierarchy for instructions on how to use the new classes and methods.

Renamed methods: NumberUtils.isFloatingPoint => TypesUtils.isFloatingPoint NumberUtils.isIntegral => TypesUtils.isIntegralPrimitiveOrBoxed NumberUtils.isPrimitiveFloatingPoint => TypeKindUtils.isFloatingPoint NumberUtils.isPrimitiveIntegral => TypeKindUtils.isIntegral NumberUtils.unboxPrimitive => TypeKindUtils.primitiveOrBoxedToTypeKind TypeKindUtils.widenedNumericType => TypeKindUtils.widenedNumericType TypesUtils.isFloating => TypesUtils.isFloatingPrimitive TypesUtils.isIntegral => TypesUtils.isIntegralPrimitive

The CFStore copy constructor now takes only one argument.

Closed issues: #352, #354, #553, #722, #762, #2208, #2239, #3033, #3105, #3266, #3275, #3408, #3561, #3616, #3619, #3622, #3625, #3630, #3632, #3648, #3650, #3667, #3668, #3669, #3700, #3701.

... (truncated)

Commits

• aa8758a new release 3.7.0
• ce954be Fix more links.
• b73b3b3 Update script.
• 525e50e Fix broken links.
• e8b512d Bump aws-java-sdk-bom from 1.11.872 to 1.11.873 (#3723)
• 12c8ab4 Prep for release.
• aa18a87 Widening for floating-point types
• 5a87df7 Javadoc changes
• 17dcfcf Flip stores when comparing to a constant
• 80cd773 Handle widening primitive conversions
• 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

[dependabot]

Superseded by #2223.