I'm specifically waiting for https://youtrack.jetbrains.com/issue/KT-12912 to reach 1.1-eap 🙂

@alexey.tsvetkov ^^

Some kapt2-related fixes are published to the

kotlin-dev

repository https://bintray.com/kotlin/kotlin-dev/kotlin/1.0.4-dev-2932. Please note it’s not

kotlin-eap

.

Good news - it works. Bad news - it has a lot of critical performance issues: 1.

compileXxxKotlin

task is about 35% slower than

compileXxxKotlin

+

compileXxxKotlinAfterJava

used to be (45 seconds in

1.0.3

vs 1 minute in

1.0.4-dev-2932

). 2. It consumes much more memory (no particular numbers, sorry). 3. I believe there is a memory leak somewhere. Gradle daemon consumes all the available memory (8GB in my case) after a few (7 - 10) successful builds and I'm not even able to compile the project anymore because everything becomes extremely slow and it takes up to 10 minutes to build the project.

4.

compileXxxKotlin

task takes 15 seconds to incrementally compile single line change

Thanks for the feedback. I'll investigate it. Be the way, what Annotation processors are you using?

only databinding

We are trying to avoid all annotations processors because of kapt bugs 🙂

New EAP build

1.0.4-eap-118

is available

is there a changelog available?

Works fine with https://github.com/sdeleuze/geospatial-messenger/

any performance improvements in

1.0.4-eap-118

?

One of the modules of my multi-module Android project which uses Dagger 2 builds fine with 118. Another which uses ButterKnife, however, doesn't. 😞 Not sure if this is a ButterKnife issue or kapt 2. Stacktrace:

@User uploaded a file: Build exception

use the latest version

OK, thanks. Should have tried that first

Jack has (had) the same problem

(disregard, user error)

The kotlin compile task is finishing successfully now, but I'm running into either https://github.com/JakeWharton/butterknife/issues/338 or some variant thereof, which doesn't manifest with kapt 1. I'll apply the workaround(s) mentioned in that bug in a bit.

(Sorry if this is considered noise, I don't want to turn this into my personal support channel. I'm mentioning it only in case it's relevant to the EAP.)

@User shared a file: and commented: Why would I use

kotlin.Throwable

when it’s missing most fields from

java.lang.Throwable

?

@denis.zharkov commented on @cedric’s file : What exactly are you missing in

kotlin.Throwable

?

@denis.zharkov

stackTrace

,

printStackTrace()

, etc… unless I misread

Actually… everything 🙂

public open class Throwable(open val message: String?, open val cause: Throwable?) {
    constructor(message: String?) : this(message, null)

    constructor(cause: Throwable?) : this(cause?.toString(), cause)

    constructor() : this(null, null)
}

@cedric In 1.0 these are extensions of

kotlin.Throwable

in stdlib, in 1.1 they are available as its own member functions.

I was wondering about that. My IDEA didn’t see them, though, maybe an environment problem

@vmironov Does the kapt2 performance issues you wrote about reproduce on any project? I spent some time analysing the project with DataBinding and Orma, and I couldn’t find any critical problems. The build time is almost equal (±1-3sec). 1GB heap, out-of-process dex. Also no problems with the memory consumption. Though the project is relatively small, ~2k lines in Kotlin.

We have only one project that uses

kapt

~45k lines of kotlin code