Ohh, there is

reduce

.

You would have to do "if index == 0" with

flatMap

. Reduce might be better for you.

It's working! If anyone's interested:

val moments: List<ListItem> = moments
        .groupBy { it.timePosted!!.toLocalDate().withDayOfMonth(1) }
        .map { it.key to it.value.map { ListItem.MomentItem(it) } }
        .flatMap { listOf(ListItem.HeaderItem(it.first)) + it.second }

Now to clean this up quite a bit, lots of stuff in there I still don't like 😄

So you want header before first element too?

Actually yes, poorly worded from my part there 🙂

@robin IMHO this is totally unreadable code - one must spend more than a 2 minutes to understand what it is it's doing. A

for

loop would be much better in this regard

Fusion of oop and fp means use what fits best in the context.

oop + fp = "foop"!

😜

@voddan could you show what would it look like with

for

?

Good question 😉 Let me try

@User uploaded a file: Untitled

@voddan Agreed, what I posted is definitely unreadable, it was just the first version that actually did what I wanted it to. This was mostly an exercise in fp for me, and from this point I'm now going to adjust this to make it actually maintainable. I never meant to put that into production 🙂

the sequence API doesn't seem to have a mechanism for batching / eachN?

something like

listOf(1,2,3,4,5).toSequence().batch(2).forEach{println(it)} => 1,2 ; 3,4 ; 5

not yet

@ilya.gorbunov see it recently? mostly simple paging…

Are there still any hopes for https://github.com/Kotlin/KEEP/blob/master/proposals/stdlib/bignumber-operations.md to make it into

The issue with BigInteger.mod is resolved in 1.1, however given that there's no prototype of other proposed functions, it's unlikely that they will make into 1.1

@ilya.gorbunov when is the feature freeze?

<!here|@here>: We need you feedback on new changes in the standard library! https://blog.jetbrains.com/kotlin/2017/01/kotlin-1-1-whats-coming-in-the-standard-library/

wow! it was posted from the future!

that’s how you know it’s going to be awesome.

Okay, first thing's first: dagnabbit Jigsaw

Is the naming of

minOf

and

maxOf

to avoid potential collisions with variables named

min

and

max

in existing code?

Starting from there

(Jump to timestamp and observe the conversation)

The naming still is a little strange to me (I remember reading that earlier, but I wasn’t active in the channel at the time).

Wouldn't it be interesting to add a few or all of the static methods in the

Files

class as extension methods on the

Path

class for the jre7 stdlib?