Is it possible to make @Nullable annotations in libraries currently not understood by the kotlin nul...

# announcements

[Leon K]

Is it possible to make @Nullable annotations in libraries currently not understood by the kotlin nullabillity annotation magic count as nullable values somehow? For context, im using a library that defines its own @nullable, and id like kotlin to consider that annotation such that my calls to annotated functions from that library are properly detected as returning nullable values.

Ive looked at the JSR305 compiler flag thingy, but im not sure if thats actually what i need here - at least it doesnt do anything, and im unsure how kotlin would know if the specified annotation is supposed to mean non-null or nullable

[Alexey Belkov [JB]]

Can you ask the library maintainer to annotate their types with JSR305 annotations so Kotlin would understand it?

[Leon K]

I guess if thats the only option, thats the only option 😕 i think they explicitly stated they want to avoid the jsr305 dependency tho 🤔

In general, i assume that implies there is no magical hidden -XImpliesNullable=fqdn.of.Annotation flag, right?

[ephemient]

https://github.com/JetBrains/kotlin/blob/master/core/compiler.common.jvm/src/org/jetbrains/kotlin/load/java/JvmAnnotationNames.kt that's the list

[Leon K]

Yea, i saw that - sadly its not including the brave logging stuff im using, so that doesnt help me

[Leon K]

So no fix? Damn, ig ill file an issue