<@U0B8UEMV1> <@U4UGS5FC7> <@UEU1NDQCD> I'm back fr...

# arrow-contributors

[addamsson]

@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?

[addamsson]

I think that the internal implementation should be refactored to use the kotlinx.collections.immutable data structures

[addamsson]

and these should be wrapped in arrow constructs

[addamsson]

I think this just depends on the level of purity you envisaged

[addamsson]

I share Rich Hickey's views in this regard:

[addamsson]

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

[addamsson]

in the meantime i'm going to speed through the Arrow docs which I skipped the last time 😄

[addamsson]

ping @Imran/Malic @pakoito @raulraja

[addamsson]

I think it is up to you to decide where we should take this since I'm just the newbie here 😄

[pakoito]

I don't have much time this days with work, I'm also behind in reviews -.-

[addamsson]

don't worry i have plenty of time

[addamsson]

i was just looking for some input so i can park / pick up this thread 😛

[pakoito]

I'd say take ListK as an example and wrap the persistent version. No new repo, just in arrow-core locally for yourself.

[pakoito]

See if you can implement both Monad and Traverse. Don't bother with the rest of the hierarchy, just implement those.

[addamsson]

good idea!

[addamsson]

that's what I did with PersistentMap as well

[addamsson]

I used MapK as inspiration

[pakoito]

👍🏼