[automerger skipped] Add apex_available to JSpecify am: 09475879d5 am: 2ec426ccac -s ours

am skip reason: Merged-In Ifaf59a839a23614a0439c0d47d0abf73abd315ae with SHA-1 a59c722e19 is already in history

Original change: https://android-review.googlesource.com/c/platform/external/jspecify/+/3346905

Change-Id: I981fd25b105ef5f583932d87c76db1e24b6077c0
Signed-off-by: Automerger Merge Worker <[email protected]>
tree: bd1727f056b8fa25d8200eed3a623a22fbc538af
  1. .github/
  2. .idea/
  3. cftojspecify/
  4. conformance-tests/
  5. docs/
  6. gradle/
  7. samples/
  8. src/
  9. .gitattributes
  10. .gitignore
  11. .ignore
  12. Android.bp
  13. AUTHORS
  14. bnd.bnd
  15. build.gradle
  16. CONTRIBUTING.md
  17. gradle.properties
  18. gradlew
  19. gradlew.bat
  20. LICENSE
  21. METADATA
  22. MODULE_LICENSE_APACHE2
  23. OWNERS
  24. README.md
  25. settings.gradle
README.md

JSpecify

An artifact of well-specified annotations to power static analysis checks and JVM language interop. Developed by consensus of the partner organizations listed at our main web site, jspecify.org.

Our current focus is on annotations for nullness analysis.

Status

Version 0.3 is relatively safe to depend on in your code. Or you can read a more detailed answer.

Things to read

See jspecify.org/docs/start-here.