@jmfayard has left the channel

We are having an issue with compiling kotlin from Intellij after the upgrade to 1.1.2 - basically what happens is that if we make a change in module 1, then module 2 that depends on it does not detect this change. However, the editor does mark the code as red and uncompilable, but "Build Project" will give happily still compile, not seeing the change in module 1. This obviously leads to runtime errors like NoSuchMethod and so on. We tried to reproduce it with a minimal project but were unable, so we are pretty much at a loss as what to do. We have been doing kotlin for more than 9 months, and we are certain it only happened after the upgrade to kotlin 1.1.2. Compiling from gradle also works just fine. Are there any debug switches or anything we can enable so we can get gather more data? As I take it it is very hard to find the bug from the info I can provide so far. I'm thinking maybe some debug output of the classes that are being recompiled upon "Build Project"? 1 reply nomad: I am having the same problem; for some reason, compiler either create or do not create

classes

and

kotlin-classes

in the output directory (In my case, gradle -> build). If it "forgots" to update one of the directories, other module will see old version of the file. Compiling from gradle works as it should, Temporary solution is to delete the build directory, but it is hard to say will problem happen again or not.

We are having an issue with compiling kotlin from Intellij after the upgrade to 1.1.2 - basically what happens is that if we make a change in module 1, then module 2 that depends on it does not detect this change. However, the editor does mark the code as red and uncompilable, but "Build Project" will give happily still compile, not seeing the change in module 1. This obviously leads to runtime errors like NoSuchMethod and so on. We tried to reproduce it with a minimal project but were unable, so we are pretty much at a loss as what to do. We have been doing kotlin for more than 9 months, and we are certain it only happened after the upgrade to kotlin 1.1.2. Compiling from gradle also works just fine. Are there any debug switches or anything we can enable so we can get gather more data? As I take it it is very hard to find the bug from the info I can provide so far. I'm thinking maybe some debug output of the classes that are being recompiled upon "Build Project"? 2 replies I have created an issue regarding this: https://youtrack.jetbrains.com/issue/IDEA-172784

what is the url for kotlin plugin dev channel? So that I can update to the latest possible version.

Are you looking for https://teamcity.jetbrains.com/guestAuth/repository/download/bt345/bootstrap.tcbuildtag/updatePlugins.xml ?

maybe, let's see...

I’ve found a cunning trick to get the Kotlin compiler to check when statements for exhaustiveness when the branches return Unit. E.g. if I have a sealed Fruit class with sub-classes Apple, Banana and Clementine, this will not be checked for exhaustiveness:

when (fruit) {
   is Apple -> printApple(fruit)
   is Banana -> printBanana(fruit)
}

But if you add a non-null assertion at the end, it will be treated as an expression, and then the compiler will check for exhaustiveness, so the code below will not compile, as one would wish.

when (fruit) {
   is Apple -> printApple(fruit)
   is Banana -> printBanana(fruit)
}!!

But IntelliJ marks the !! with an unused code warning.

I’d really like a way to turn off that warning for the project, for this specific case of non-null check.

Cant you just do

.apply{}

instead or something similar ?

@natpryce you could define a method

inline fun Any.check() {}

and call that instead of !!

Similar code detection does not seem to work in Kotlin as Java. Is there a special thing I need to do to make it work? Or is it a feature not yet added to IntelliJ?

no, it's not implemented yet

@mikehearn has left the channel

@christophsturm we do have just such a method … but why reimplement something that’s already in the language?

@natpryce (stating the obvious:) to avoid the warning?

I’ve got a Kotlin class which extends a Java class, e. g.

// Java
public class Something {
    public String getValue() {...}
}

// Kotlin
class SomethingCool {
    @Deprecated(..., ReplaceWith(...))
    override fun getValue(): String = ...
}

Getting this issue:

SomethingCool().getValue() // got quickfix from ReplaceWith
SomethingCool().value // no quickfix

Is it known issue or should I file a new one? Or I’m doing something wrong?

looks like a new issue to me

@christophsturm yes, that's why we wrote such a function (we called it

exhaustive

). My request is for this use case of !! not to flag a warning, so that we don't have to have a function that duplicates something in the language.

@natpryce makes sense. I think the warning is just a bug because it’s clearly not unused code if it changes the behavior of the compiler

Should type hints be displayed for

Unit

returning functions?

fun foo() <hint>: Unit</hint> = bar()

Currently they are, not sure if good or bad

I think they should. it's not obvious in such an expression that the return type is

Unit

a bit offtopic but don't type hints strike you as a bit ironic considering how type inference is all about removing type declarations from your code?

I actually like them and they are updated automatically when the inferred type changes which leaves the user with the best of both worlds

but just a thought that crossed my mind

@jchildress has left the channel

Does the community version of IntelliJ IDEA come with full Kotlin support? JS support seems to be listed in the ultimate section of comparison matrix.

@kirillrakhman I don’t agree

I think type inference is mostly about readability