Thanks @amaranth 😄

the idiom for that is

(0..size - 1).map {"Hello"}

but I agree that we need something more discoverable

@debug: ^^

@voddan cool stuff!

I had been playing around with ranges but you made me realize I had been forgetting to put the brackets around them and the autocompletion was always looking up the

Int

and the not the resulting range. 😛

@voddan

(0 until size)

TIL until

fun <T> mutableListOf(size: Int, init: (Int) -> T): MutableList<T> = if (size == 0) ArrayList() else (0 until size).mapTo(ArrayList(size)) { init(it) }

That got a lot simpler

IMHO it should be in line with

Array(10) {0}

, e.i.

List(10) {0}

Personally, I prefer

repeat(size)

over

(0 until size)

Same, although it's not always usable like that

We didn't make it public because we hadn't felt there are compelling use cases for it. What's yours?

@ilya.gorbunov: I need to write a generic method that checks if a value is set, and

null

is potentially a valid value

Not just checks but gets the value

@Eugenio: That's what this function does, but what are your more high-level goal? (if you could tell)

If you can use Java 8 you can just use Map’s getOrDefault

Heh, the default method for that on Map is basically identical to getOrElseNullable

Sure, I'm writing a Redux port in Kotlin and when doing the

combineReducers

implementation I need to know exactly if a value was set (even if

null

) otherwise the relative reducer will have to initialise its own state: https://github.com/Takhion/Redux.kt/blob/master/src/main/kotlin/me/eugeniomarletti/redux/internal/CombinedReducer.kt#L19

Of course adding

inline

but this would be really cool to have

Maybe even make it

tailrec

Honestly, looks like a not very useful feature 🙂

still missing https://youtrack.jetbrains.com/issue/KT-12109

should we create a proposal for it?

I am confused with this Immutable Collections proposal when Google Guava exists, which got no mention. What's the reasoning? https://github.com/Kotlin/kotlinx.collections.immutable/issues/7

For instance, using immutable collections in JS applications.

And I would prefer not to use Guava on Android.

Anyway, it seems to be a good idea to have a good ecosystem for a language that tends to be a cross-platform language.

Main point of the proposal is to make APIs standard, so that various implementations can be interoperable. One can implement same APIs using Guava.