Channels
#language-proposals
- d
damian
11/18/2015, 7:26 PMThat's a good point, regarding comparison operators, but it does cause unnecessary allocations (consideration for Android and memory/performance critical applications) - v
voddan
11/18/2015, 7:28 PMcan't it be inlined? - v
voddan
11/18/2015, 7:28 PMlike in
loopsfor - v
voddan
11/18/2015, 7:29 PM@udalov: could I heard somewhere that constant ranges are being inlined? likeif(2 in 1..3) - d
damian
11/18/2015, 7:38 PMWhat about non-constant (but never assigned) ranges? Would it be possible to inline those? (e.g.
)if (2 in 1..n) - v
voddan
11/18/2015, 7:45 PMif think they are planning something like that, there was a talk about efficient collection slicing aka python - v
voddan
11/18/2015, 7:46 PMone way to implement it is
->list[1:10]list(1, 10) - v
voddan
11/18/2015, 7:46 PMdonno - d
damian
11/18/2015, 7:46 PMactually, looking at the bytecode, it seems that they are already inlined - v
voddan
11/18/2015, 7:47 PMthought so - v
voddan
11/18/2015, 7:47 PMbut anyway impressive - v
voddan
11/18/2015, 7:48 PMi thing it shoul a separate topic in the docs - d
damian
11/18/2015, 7:50 PM-.scala - v
voddan
11/18/2015, 7:52 PMThat's why they neededIntRange - v
voddan
11/18/2015, 7:53 PMso what aboutobject INF - v
voddan
11/18/2015, 7:54 PMfun INF.rangeTo(x: Int) = IntRange(Int.MIN_INT, x) - v
voddan
11/18/2015, 7:54 PMfun Int.rangeTo(i: INF) = IntRange(this, Int.MAX_INT) - d
damian
11/18/2015, 7:59 PMSeems
creates an instance, butIntRange
is inlinedoperator fun Int.rangeTo(inf: INF) = this..Int.MAX_VALUE - v
voddan
11/18/2015, 8:02 PMwow - v
voddan
11/18/2015, 8:02 PMmagic everywhere - v
voddan
11/18/2015, 8:03 PMwill you submit that ? I don't want to be the one to do that 😉 - d
damian
11/18/2015, 8:06 PMSubmit? Referring to the proposal from earlier or something else? - v
voddan
11/18/2015, 8:36 PMye, if you like the idea. For me it is too crazy - d
dmitry.petrov
11/20/2015, 11:59 AMActually, there is some "magic" in 'for' code generation that handles range literal (with const bounds or not) as a special case. - v
voddan
11/22/2015, 3:08 PMokydoky - v
voddan
11/22/2015, 3:09 PMwanna talk about java interop and SAMs - v
voddan
11/22/2015, 3:11 PMnow Kotlin supports a convention that if you interop with Java, and want to pass a lambda, instead of casting it to an interface you put the interface's name before it:Drawable {a -> 239} - v
voddan
11/22/2015, 3:11 PMit works as the kotlinc generates such functions for you, so
is a factory function invocationDrawable {} - v
voddan
11/22/2015, 3:14 PManswering a question on SO I found three huge problems with that convention, and now I propose to remove it in favor of explicit casting{a -> 239} as Drawable - v
voddan
11/22/2015, 3:15 PMProblem 1) it is hard to read: I expect an interface implementation, but I get this
"function" invocationDrawable