Commits on Jun 26, 2024

1. Use JSpecify annotations in the public release. …

   We've been using these internally for over a year. With JSpecify 1.0 not far off and wider adoption to gradually follow, now seems like the time to expand our public usage of the annotations. We've already been using them in a few projects, but Truth may become the mostly widely used project that users actually link against to use them. At the same time, it's a library that's used only in testing code, so the stakes remain relatively low.
   
   Most users will see no effect from this change, since most users don't use nullness checking and since we already used some nullness annotations in our public release. The main effect users are likely to see is if they pass nullable values for parameters that are now recognized as non-nullable. Under Kotlin, the effect should normally be a warning, not an error, at least until [Kotlin 2.1 or so](https://youtrack.jetbrains.com/issue/KT-55586/Handle-nullability-from-jspecify-annotations-properly#focus=Comments-27-8368666.0-0). Please still [report any problems](https://github.com/google/truth/issues/new).
   
   (progress toward JSpecify adoption in our projects in general, including google/guava#2960)
   
   RELNOTES=Added more nullness information to our APIs (in the form of [JSpecify](https://jspecify.dev/) annotations). This could lead to additional warnings (or even errors) for users of Kotlin and other nullness checkers. Please [report any problems](https://github.com/google/truth/issues/new).
   PiperOrigin-RevId: 647012817

   

   cpovirk authored and Google Java Core Libraries committed Jun 26, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for ee680cb
   • Browse repository at this point

   Copy the full SHA

   ee680cb View commit details

   Browse the repository at this point in the history