https://kotlinlang.org logo
#arrow-contributors
Title
# arrow-contributors
a

addamsson

08/06/2019, 9:43 AM
@pakoito @raulraja @Imran/Malic I'm back from vacation! What do you think about rewriting the internals of the persistent collections PR in the light of recent improvements to
kotlinx.collections.immutable
?
🎉 2
I think that the internal implementation should be refactored to use the
kotlinx.collections.immutable
data structures
and these should be wrapped in arrow constructs
I think this just depends on the level of purity you envisaged
I share Rich Hickey's views in this regard:

https://www.youtube.com/watch?v=E4RarTAZ2AY&feature=youtu.be&t=2654

in the meantime i'm going to speed through the Arrow docs which I skipped the last time 😄
😄 2
ping @Imran/Malic @pakoito @raulraja
I think it is up to you to decide where we should take this since I'm just the newbie here 😄
p

pakoito

08/07/2019, 3:48 PM
I don't have much time this days with work, I'm also behind in reviews -.-
a

addamsson

08/07/2019, 3:51 PM
don't worry i have plenty of time
i was just looking for some input so i can park / pick up this thread 😛
p

pakoito

08/07/2019, 4:30 PM
I'd say take ListK as an example and wrap the persistent version. No new repo, just in arrow-core locally for yourself.
See if you can implement both Monad and Traverse. Don't bother with the rest of the hierarchy, just implement those.
a

addamsson

08/07/2019, 4:59 PM
good idea!
that's what I did with
PersistentMap
as well
I used
MapK
as inspiration
p

pakoito

08/07/2019, 6:24 PM
👍🏼
2 Views