Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.

...

1 commit
1 file changed
1 contributor

Commits on Jul 23, 2025

[Xamarin.Android.Tools.Bytecode] add `org.jspecify.annotations.NonNul…

…l` (#1351)

Context: https://mvnrepository.com/artifact/org.jspecify/jspecify
Context: https://mvnrepository.com/artifact/org.jspecify/jspecify/1.0.0/usages
Context: https://github.com/JetBrains/kotlin/blob/03360c0108797b2a98b6608e2bddfacd5f4e87ce/core/compiler.common.jvm/src/org/jetbrains/kotlin/load/java/JvmAnnotationNames.kt#L64-L91

It appears that some newer AndroidX/GPS libraries are now using:

```diff
--androidx.annotation.NonNull
++org.jspecify.annotations.NonNull
```

I can see versions of guava and androidx.core taking a dependency on
`org.jspecify:jspecify:1.0.0`, which provides the
`org.jspecify.annotations.NonNull` annotation type.

I sorted the list of annotation types alphabetically, and added the
`org.jspecify.annotations.NonNull` annotation type to the list of
recognized annotations in `XmlClassDeclarationBuilder.cs`.

So, then we found a list of "non-null" annotations in the Kotlin
compiler. Updated to include some of the ones they list as well.

jonathanpeppers committed Jul 23, 2025