Makes variance annoying in Kotlin... seems I need something like

@Suppress("UNCHECKED_CAST")
fun Parcel.writeTypedSparseArray(value: SparseArray<*>) = writeSparseArray(value as SparseArray<Any>)

I take it we need to write our own iterators for sparse array?

@spand has left the channel

If I use any Crash Reporting Tool like Firebase, will I get proper line numbers that map to the actual ones in Kotlin .kt files?

@rakshakhegde: yes, can’t speak for Firebase, but definitely true for Crashlytics with and without proguard.

cool

compiler puts correct mapping to source files into bytecode so stacktraces point to correct lines, should work with any tool that supports java stacktraces I guess.

you may get confusing line numbers for inline methods, especially when nesting them like:

measureTimeMillis {
    foo.forEach {
        it.doStuff()
    }
}

But at least in the stack trace I will get something that points to

measureTimeMillis

right?

Looks like Android Gradle 2.0.0 is still the only version that works with Kotlin https://youtrack.jetbrains.com/issue/KT-12113

Hmm, I use 2.1.0 with Kotlin 1.0.2 and it seems to be fine... I can

./gradlew clean build

from the command line too

same

doesn't work for me in console

running in studio works fine, trying to build from command line fails

and running espresso tests fails too

important note - I also use databinding

@rakshakhegde: If doStuff() is a inline function you will get the line number where doStuff is defined but no the reference to it.doStuff() inside forEach loop. But its the same behaviour as the local stack trace. Firebase will just send that stack trace to the server.

@rakshakhegde: yes, probably pointing to

kotlin.system.TimingKt

I wish 1.0.3 will solve all this compatibility problems with android gradle plugin, databinding and dagger

What issues are you having with Dagger?

Dagger’s working fine for me with Dagger 2.4 and Kotlin 1.0.2

It's a combination of everything, dagger just plays a part android gradle 2.1.2 with kotlin 1.0.2 and dagger 2.4 gives NonExistentClass that I couldn't workaround

dagger <2.4 not working because of some guava issue that was fixed only in 2.4

-.kt

Try using kotlin

1.0.2-1

That fixed the

NonExistentClass

issues for me (they were intermittent before)

@rnowif has left the channel

@nphumbert has left the channel

Here is a weird issue I’ve got with Dagger 2: https://youtrack.jetbrains.com/issue/KT-12432

@brianwernick: I’m using Dagger 2.2 (by Google) + Kotlin 1.0.2-1 without any problem

But I create my modules in Java, with Kotlin it doesn’t work.