What is the stat of adopting `kotlinx.collections....

# arrow

[Ulrich Schuster]

What is the stat of adopting kotlinx.collections.immutable in arrow? It seems that PersistentList would be an ideal implementation for NonEmptyList, for example.

[Youssef Shoaib [MOD]]

Since PersistentList is just a List, you can have it inside a NonEmptyList just fine.
Maybe a compatibility module could be nice?

[simon.vergauwen]

Is this related to Compose i.e. PersistentList being stable and List not being stable? I'd love to solve that actually but I'm not a big fan of introducing a dependency into core even if it's a kotlinx dependency.

> Since PersistentList is just a List, you can have it inside a NonEmptyList just fine.
I think you lost stability guarantees for compose here.

[Ulrich Schuster]

For me, it's pure backend server-side development, with the goal to be functional, immutable, and performant 😉

[Alejandro Serrano.Mena]

as @Youssef Shoaib [MOD] mentioned, you can use any underlying List implementation you want in NonEmptyList, that's what the wrap family of functions is for