This is just insane. Once in a while everythin in build.gradle.kts becomes red for no reason, and then some minutes later randomly goes back to normal

@barteks2x uploaded a file:

@barteks2x uploaded a file:

@barteks2x uploaded a file:

This is not right... so is the

!!

needed or not?

Depends on the definition of

sourceSets

of cours, I'd file a YouTrack issue.

the definition seems to be in java

public SourceSetContainer getSourceSets() {
        return sourceSets;
    }

the

sourceSets

field is final

Anyway, with the experience I previously had with reporting bugs to jetbrains I'm not going to bother with it

@barteks2x Huh? They (the Kotlin and Idea teams at least) always respond very quickly to YouTrack issues in my experience.

Is there anything that needs to be configured for code coverage to be reported for inline functions?

My guess is there isn’t enough context after compilation for code coverage to be reported, but figured I’d check

inlined functions don't exist at runtime as such

Afaik there is no code coverage tool that supports kotlin source files

Would be cool if there was a compiler annotation to disable inlining other functions in the current function, altrough that still wouldn't work for

reified

functions.

At the

for

loop here IDEA suggest me to change to using `any{}`: https://www.dropbox.com/s/ht885r4exwk4ege/Screenshot%202017-10-16%2015.48.20.png?dl=0

I believe it should suggest me to use

all{}

instead

This is what the result of applying the suggestion: https://www.dropbox.com/s/k1dwggcpu5bnabf/Screenshot%202017-10-16%2015.52.15.png?dl=0

ah, ok, there's a issue for it, thank you.

Have a sticky situation where I have cloned a Git repo and imported it into IntelliJ by selecting the pom.xml file in the root dir. After importing the repo an attempt was made to create a new Gradle project (via Gradle Kotlin DSL), however IntelliJ doesn't recognise the new dir as a Gradle project. Gradle works fine with the new project via the terminal without any issues. Is there a need with IntelliJ to start from scratch in order to resolve the issue?

Decided to start from scratch again by importing the repo via dir selection in IntelliJ, and selected the second Gradle option (first two options are called Gradle 😕 ). The new directory isn't recognised as a Gradle project, however the build.gradle.kts file is now recognised after restarting IntelliJ.

Latest attempt doesn't work as expected with Gradle not refreshing the project in IntelliJ. Now imported the repo in IntelliJ once again, this time selecting the new project's build.gradle.kts file. Now IntelliJ recognises the project as a Gradle project, and doing a Gradle refresh works as expected (build.gradle.kts file is also recognised). Had to click on the popup link to import the missing Git VCS root in order to ensure the repo is properly recognised by IntelliJ.

Why is the

Tools/Kotlin/Decompile Kotlin to Java

option greyed out?

usually I've observed it when there is some problems with kotlin code and it can be compiled

I didn't know you could do that in one step, I've always done Kotlin -> Bytecode -> Java

is this a bug? If I do take the advice, it replaces

?:

with

==

which is not my intention here.

for a

foo: Boolean?

,

foo ?: false

is equivalent to

foo == true

, and the latter is preferred according to the Kotlin style guide

ah, ok, but reads somewhat harder in my opinion