also <@U0BHS1Y07> I couldn't disagree about immuta...

# stdlib

[groostav]

also @voddan I couldn't disagree about immutable collections more. I can (and do) use immutable collections over mutable collections by default. The reason is because it typically starts to clarify what the rust guys would call "ownership semantics"; exactly who is adding data where becomes much more evident with persistent collections than mutable ones. Debugability also typically goes up when you can be certain that collection instances wont be changed. You do start to see some pressure on return types to keep up as what might, with mutable collections, be a modified-by-reference list now becomes a new returned list instance, meaning fun someFunc(): Pair<SomeModel, List<OtherModel>> becomes more common, but thats also a move to more pure functions which im totally in favor of. Unfortunately, when you want to use one of the ol' java.concurrent.collections or some other java-centric APIs I'm forced back into mutable land.