are there plans to merge kotlinx.collections.immu...

# stdlib

[christophsturm]

are there plans to merge kotlinx.collections.immutable into the kotlin stdlib or is it just an experiment?

[ephemient]

why are those the only options? it could be non-experimental and external. kotlinx.coroutines isn't in stdlib either.

[christophsturm]

I’m also interested in any other answer 🙂

[sergio mongelat]

I'm interested in why aren't coroutines in the stdlib

[ephemient]

well at a first glance, kotlinx.coroutines uses kotlinx.atomicfu which isn't in stdlib either

[araqnid]

one reason (aiui) is so that the coroutines lib can evolve at a faster pace than stdlib (which itself evolves faster than the core language)

[araqnid]

I guess it also makes things like maintaining the interop components easier to manage without making a load of external libraries dependencies for working on stdlib

[louiscad]

If you read the KEEP on value classes, it'll answer your question 😉

[christophsturm]

you could just tell me if you already know 🙂

[Zhelenskiy]

@louiscad The KEEP is rather big 🤨 so if you know, it would be great to say it here 😌

[louiscad]

@christophsturm @Zhelenskiy Here's the anchored link that talks about "value interfaces": https://github.com/Kotlin/KEEP/blob/master/notes/value-classes.md#value-interfaces

For the lists case, there would be mutable and immutable modifiers for the List type instead of current MutableList from stdlib and ImmutableList from kotlinx.

[christophsturm]

sounds great