listOf<String>().contains(Any())

cmd+B into

contains

to see the code. Hint:

@kotlin.internal.OnlyInputTypes

.

Am I overlooking it or does Kotlin really not provide collections with lazy stream operations like Java 8 or C# LINQ? Seems better to assume that people don't want to create a new ArrayList every time they "apply" something like a filter, instead making this an option like

IEnumerable.ToList()

or Java's collectors, no? I guess it's not a big deal but it kind of discourages consistent chained collection processing like you see in C# (where it scales). I guess it's not idiomatic Kotlin - I'm just surprised given that this is even idiomatic Java now

with

asSequence()

you can switch from eager evaluation to lazy

Oh thanks! One of these days I'll find something wrong with Kotlin...

Hey! I have a

kapt

weirdness. I have a Kotlin class that extends another class, and if I look at the generated kapt stub, it doesn’t extend it (which causes problems later). Is this a known bug?

(also, I’m not sure if I’m supposed to use

apply plugin: 'kotlin-kapt'

or not)

newbie question, is there a one-line was of changing IntArray to DoubleArray?

I expect

(0..10).map(Int::toDouble)

would probably work

Didn't check though

Foo Bar, that will create a

List<Double>

This ought to do it

fun convert(ints: IntArray) = DoubleArray(ints.size) { index -> ints[index].toDouble() }

Error:(7, 88) Kotlin: Type inference failed. Expected type mismatch: inferred type is List<Int> but Collection<Int> was expected

@farleylai commented on @farleylai’s file : Very strange in the task2 of Koans offline with IntelliJ. The online version shows no such errors. Any ideas?

@farleylai commented on @farleylai’s file : Figured out. The original Java imports should not be copied. The Collection type should use Kotlin version accordingly. import java.util.Collection; import java.util.Iterator;

@User uploaded a file:

@User uploaded a file:

I think you are supposed to use

@JvmName

No, you should write a custom setter on the prop

So

var prop: String? = null
   set(newValue) {
    }

Looks like a bug may be. JVM allows it because return value is different.

int i = new K().setProp(null);

This should work?

No, trying to assign it to int doesn't change anything in Java.

Yup, thanks.

uhh

how do I write code

ah, got it

is there a way to shorten this?

@argoneus directly call refresh_servers from XML. No need for findViewById.

@sagar.atalatti directly call?

I work with srl later in the function