Fixed
Status Update
Comments
ju...@google.com <ju...@google.com>
ju...@google.com <ju...@google.com>
ju...@google.com <ju...@google.com> #2
I don't think the average developer understands the distinction between method references and method definitions in this context (inside a DEX file). I know I don't.
@jvg, can you elaborate?
an...@google.com <an...@google.com> #3
people who are looking at the bytecode in the dex to optimize their app through shrinking hopefully will learn the difference as string tables for method references between various dex files can account for quite a bit of disk space. but more importantly a definition is something you can analyze its code for where a reference you can't so the UI can be confusing without seeing the difference
Description
Follow up to b/345452195 , which addressed false positive UnknownNullness lint errors on java code using type-use nullness annotations.
The UnknownNullness lint also comes up when kotlin code implicitly uses an unannotated java type, and that case does not currently handle type-use annotations.