the compile time is so bad in kotlin. 25s for measly 300 lines of code + 1 library. insane.

@ilya.gorbunov that's running the code, not creating the function reference

k, thanks!

@chb0kotlin Technically it is a constant but not for the compiler

Would be great, foo bar

I have the book, will check it out too @agomez!

do I have to override toString for each of the contained subclasses...?

guys, how do i reverse this:

return this.sortedWith(
                compareBy(
                        { it.isFriendOnline },
                        { it.presenceMode },
                        { it.gameStatus },
                        { it.name }
                )
        )

my interface: interface UrlContentRetrieved { fun onUrlContentRetrieved(content: String) } java code: task.setListener(new UrlContentRetrieved() { @Override public void onUrlContentRetrieved(String content) { parseResults(content); } }); is converted to task.listener = UrlContentRetrieved { content -> parseResults(content) } and i got error Error:(31, 25) Interface UrlContentRetrieved does not have constructors

Is there a way to have a static method in Kotlin?

Hi. New to Kotlin. Looks interesting 🙂

Are the differences between 1.1.2-3, 1.1.2-4, and 1.1.2-5 documented somewhere? I'm seeing lots of surprising NPEs in code when running under 1.1.2-4 that I don't see with 1.1.2-3 or 1.1.2-5.

And fragments are a pain, you should use screens and views

it seems that Kotlin/JS is getting an array literal syntax in 1.2 but Kotlin/JVM is not?

Hello guys, given Java interface

interface Foo { int bar(); }

why do I need an explicit labeled return in Kotlin when using SAM conversion when creating a property - instance of this interface:

val foo = Foo { return@Foo 5}

why cannot I just write:

val foo = Foo { return 5 }

I know that I can just write it as

val foo = Foo { 5 }

, but I wonder why I need the labeled return in the second example

anotate the method inside a companion object with

@JvmField

I'm getting a

Unresolved reference: onEach

after updating to

1.1.2-4

. The code compiles and runs fine on

1.1.2-3

. Is that a known issue?

on clean new kotlin project I get unresolved reference for kotlin.streams

I have questions on Kotlin Features Survey 1-Static members in Kotlin classes #17 why people doesn't want it? 2-Optional (trailing) commas #11 what is this feature? 3-Collection comprehensions #7 what is this feature?

without @JVMStatic you have to write employee.companion.name

I mean, I know there is interoperability, it’s just verbose sometimes. I dislike creating companion object just to declare fields that I know would be static in Java, and don’t really fit outside of the class

i can have a companion object implement an interface and interact with its instance-less methods via abstraction

@jw I see your point. I wonder, is there an example of how you’d go about using companion object that implements an interface that shows how it’s useful?

extension functions in Kotlin are the nicest I've seen

about the features, being an F# dev for long time, the only thing I really, really miss in Kotlin (after a couple of weeks of learning it 🙂 is pattern matching. Another (less severe one) is a lightweight syntax for unions.

Huh why are people against private member access in tests?

As they pointed out, they conflated optional trailing commas and optional commas in general in the options, which means they can't read too much into those. I don't think anyone wants the latter, but I think the former would be really nice

As far as I remember, optional commas was for list of declarations, not argument lists. E.g. primary constructor params.

Suppose for a class ABC, what does fun ABC () mean? Constructor are defined in a different way in kotlin