well, our opinion is different 🙂

so if

it

is

null

here, you'd be doing

null == true

, something to get used to I guess

Boolean?

can have three states,

true

,

false

and

null

.

== true

expresses clearly, that you're only interested in one of the states

It may look weird at first, because

== true

is never useful in Java

can I temporarily configure Kotlin in a Maven project without altering the Maven pom.xml file?

no

(well, depending on what you want to accomplish. if you don’t need things to build and only need to see non-red code in the IDE, you can add a kotlin-stdlib dependency in the project structure dialog manually)

thanks Dmitry, yeah I needed things to build.. I let it configure it via Maven and won't commit the file. thats ok

Does anyone know how to configure IDEA to treat inferred nullability annotations in Java libraries as explicit nullability for calls from Kotlin code?

@Bob commented on @Leon Linhart’s file : I don't really have a good answer for you, but I can tell you both 2017.2.5 and the 2017.3 EAP do exhibit your desired behavior for me. Just taking a stab in the dark - are you using external annotations (i.e. not the 'org.jetbrains' ones)?

@yole commented on @Leon Linhart’s file : inferred nullability annotations? that is not possible. nullability inference isn't performed at all when you're building code outside of IDEA

@Leon Linhart commented on @Leon Linhart’s file : A little bit more detail: - The library is written in Java and the function's first parameter is not explicitly annotated. - IntelliJ's code analysis (correctly) infers the

@NotNull

annotation. - IntelliJ provides an inspection that reports calling such functions from Java code. (Left image) - The inferred annotations are ignored for Kotlin inspections. So what I should have been asking for is: Is there an option to treat inferred annotations as explicit when inspecting type nullability in Kotlin code?

@yole commented on @Leon Linhart’s file : once again: IntelliJ's code analysis is not performed when you compile your code from Gradle or the command line. in Kotlin, nullability is not an inspection feature, it's a compiler feature. and you don't want to have code that is highlighted as valid in the IDE and fails to compile from the command line

@Leon Linhart commented on @Leon Linhart’s file : 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.

Well the actual method contract might not guarantee non-nullability while the current implemetation does, which would break compatebility.

@karelpeeters Thank you for bringing this to my attention. This did indeed not come to my mind sooner (because this is not the case for the code I was messing with). Thanks and sorry for wasting your time guys.

@beholder commented on @Leon Linhart’s file : If only we could attach our own nullability annotations to third-party libraries...

That used to work apparently: https://discuss.kotlinlang.org/t/nullable-definitions-for-java-library/2375/5

Yeah, I feel like JetBrains kinda took the easy way out on this one.

Any ideas on solving this one ?

> Could not find method cd() for arguments [unspecified] on root project

Already googled … nothing I could see that was relevant

Where does that error come from?

comes from trying to compile my project

So from gradle? Can you run it with debug info on?

I’ve discovered that the generated

build.gradle

starts with

cd version '1.0-SNAPSHOT

so I’ve commented that out

@baob uploaded a file:

generated by what? this is not valid gradle syntax

generated by intellij

how exactly did you create the project?

within intellij, I closed all windows and then chose ‘create project’ and chose gradle and within that kotlin … I think after that I chose an ‘artifact-id’ but left the ‘group-id’ blank. That’s all I can remember going through

Guys, I’m writing code but Intelij still runs old version