tschuchort
09/29/2019, 10:34 PM@NonNull
annotation on a parameter even though documentation (and common sense) says that it can be null. If I make the same parameter nullable in my overriding Kotlin method, the compiler complains to me that I'm not overriding. But if I don't, then the function will crash at the hidden parameter assertion that is generated automatically. How do I tell the compiler "shut up, I know what to do"? Can I disable null-assertions for just this method?Kirill Zhukov
09/29/2019, 11:05 PM@Nullable
, so if have access to it you can fix that.tschuchort
09/29/2019, 11:05 PMtschuchort
09/29/2019, 11:06 PMKirill Zhukov
09/29/2019, 11:07 PMKirill Zhukov
09/29/2019, 11:07 PMtschuchort
09/29/2019, 11:09 PMtschuchort
09/29/2019, 11:10 PMKirill Zhukov
09/29/2019, 11:15 PMtschuchort
09/29/2019, 11:17 PMKirill Zhukov
09/29/2019, 11:18 PMtschuchort
09/29/2019, 11:18 PMtschuchort
09/29/2019, 11:19 PMKirill Zhukov
09/29/2019, 11:21 PM4.7.1
is the latest released version, it has Timber written in Kotlin.tschuchort
09/29/2019, 11:22 PMTimber.Tree.log(int priority, @Nullable String tag, @NotNull String message, @Nullable Throwable t)
tschuchort
09/29/2019, 11:23 PMtschuchort
09/29/2019, 11:26 PMKirill Zhukov
09/29/2019, 11:29 PMtjohnn
09/30/2019, 6:13 AMtschuchort
09/30/2019, 10:34 AM