<@U4NLYMY9X> commented on <@U4NLYMY9X>’s file <htt...

# intellij

[user]

@Leon Linhart commented on @Leon Linhart’s file

https://kotlinlang.slack.com/files/U4NLYMY9X/F7MKN8BJQ/pasted_image_at_2017_10_20_08_07_pm.png▾

: Your response makes me believe that I'm phrasing my situation very poorly. If that is indeed the, I'm sorry. However, I do understand what you lined out and I do not ask for "wrong" code to be considered valid in the IDE. So let me give it one more go:

Passing null to a platform type (T!) or passing a platform type to code that is not null safe is perfectly fine and accepted by the compiler, since T! may be either T or T?.
Since IntelliJ is capable of inferring nullability annotations for types in Java would it not be logical to (optionally) consider them to be part of the nullability contract of a said type representation when used from Kotlin? (Say an inspection similar to Java > Probable bugs > Constant Conditions & exceptions?)

My initial question was whether such an inspection exists. I assume it does not at this point. Once again, I want to apologize for any misunderstandings that my wording might have caused.