Commit 4d015ca
committed
[Xamarin.Android.Tools.Bytecode] add
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.org.jspecify.annotations.NonNull (#1351)1 parent 03cb8e2 commit 4d015ca
File tree
1 file changed
+9
-3
lines changed- src/Xamarin.Android.Tools.Bytecode
1 file changed
+9
-3
lines changedLines changed: 9 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
499 | 499 | | |
500 | 500 | | |
501 | 501 | | |
| 502 | + | |
502 | 503 | | |
503 | 504 | | |
| 505 | + | |
504 | 506 | | |
505 | 507 | | |
506 | | - | |
| 508 | + | |
507 | 509 | | |
| 510 | + | |
508 | 511 | | |
509 | | - | |
| 512 | + | |
510 | 513 | | |
511 | | - | |
| 514 | + | |
| 515 | + | |
512 | 516 | | |
| 517 | + | |
| 518 | + | |
513 | 519 | | |
514 | 520 | | |
515 | 521 | | |
| |||
0 commit comments