Guys, I have a

0..12

IntRange and I want to create an IntArray initialized with values from 0 to 12. Can I do it without for loops?

Is 12 a constant?

yup

Then initialize the array with constants?

Other than that, not sure how you could avoid a loop

@cedric: is

(0..12).toArrayList().toIntArray()

less optimized than a create a 0-inited array, and initialize with a

for i in 0..12

?

how_about_this_.txt

@damian: is

IntArray(size()) let {

the same of

IntArray(size()).let {

 ?

Alex you can view byte code or the implantation easily enough.

Then you know what is efficient or not, and what the implementation is.

And yes those are same, '.' is optional for infix notation, for things that allow it.

@apatrida: you’re right: I always forgot the bytecode function of the Kotlin plugin! 😥

@apatrida: «  show kotlin bytecode » is disable on android studio

No idea, for his questions he can try in community edition, and also request a way to enable "show kotlin bytecode" as a request to YouTrack.

I think either of those is better than asking us to run "show kotlin bytecode" for questions that require that to answer.

@mboudraa:

show kotlin bytecode

is working for me in android studio (currently running canary)

Under

Tools -> Kotlin -> Show Kotlin Bytecode

(you must currently be editing a kotlin file)

@damian this is exactly this option which is disabled. And Im in the canary version too

@mboudraa: it’s enabled for me too in AS ; are you highlighting a kotlin file when opening the menu ?

@desseim: well played. I feel ashamed

I didn’t even know of this functionality before it was mentioned here >_<

Recently I've found really great thing in kotlin stdlib. TODO! But currently it has two overloaded versions:

public fun TODO(): Nothing = throw NotImplementedError()

public fun TODO(reason: String): Nothing = throw NotImplementedError("An operation is not implemented: $reason")

How about making only one version? Something like:

public fun TODO(reason: String? = null) = throw when (reason) {
    null -> NotImplementedError()
    else -> NotImplementedError("An operation is not implemented: $reason")
}

Single version will make

Find Usages

simplier.

Since we have

lateinit

, I wonder when using

Delegates.notNull()

or

lateinit

Any Idea ?

@alexander.asanov:

Find usages

could find usages of all overloads of TODO. Though it doesn't due to a bug, but eventually it should simple smile

@ilya.gorbunov: Will

Find usages

eventually find all overloads of all methods always? Or there will be an option?

@alexander.asanov: It is an option in

Find Usages Advanced

(Ctrl+Shift+Alt+F7), but once you have checked it, it affects subsequent

Find Usages

as well.

@antonioleiva: nice post you wrote about kotlin collections here http://antonioleiva.com/collection-operations-kotlin/ what about integrating it in official kotlin API docs.? Current API docs are really a pain to read and understand

thanks, I think there are still some new ones missing from M14, need some more time to review them

Hello. I understand that the Immutable Collections library is not part of the stdlib, but I am not sure where else to ask this question. Do you have any information on when the final version of the library will be released?

Why do inline classes do implement toString using the wrapper and not just the value. E.g. in

@JvmInline
value class Area(val name: String)

"Area(name=foo)" instead of "foo". Aren't they meant to provide just some typesafe wrapper while inline the value whenever possible?