sbt VS kotlinx.collections.immutable

NOTE: I won’t mention SBT and Leiningen here because, with all due respect, they are niche build tools. I also won’t discuss Kobalt for the same reason (besides, it’s no longer actively maintained). Additionally, I won’t touch upon Bazel and Buck in this context, mainly because I’m not very familiar with them. If you have insights or comments about these tools, please feel free to share them in the comments 👇

Sbt has the primitives that would allow that, but this would change the semantics of the test task. See also testQuick and https://github.com/sbt/sbt/issues/6292

If I use IntelliJ then apparently sbtn is not supported and they don't bother with Scala-CLI or Coursier.

Version 1.3.13 has a size of 1.17 MB in zip

See scala-xml 2.x mega tracker on plugin ecosystem conflicts.

This is under discussion at https://github.com/sbt/sbt/issues/6997

See https://github.com/playframework/playframework/issues/10572 and https://github.com/sbt/sbt/issues/6235 for more details and context.

BTW, if you're curious, it appears OP is using this: https://github.com/sbt/sbt/releases/tag/v1.6.2 Pretty sure one of the executables is doing ANSI colours.

If you see the progression of documentation changes over the years pushing people towards multi-project style, and issues like https://github.com/sbt/sbt/issues/6217, hopefully you'd see that I've really tried to encourage people to use multi-project style from the get go.

Fyi in case anyone is curious, sbt is fully removing log4j going forward: https://github.com/sbt/sbt/pull/6726

In Clojure, it is called an Atom. I created my own via AtomicReference and https://github.com/Kotlin/kotlinx.collections.immutable. It works really well in Kotlin. It works especially well if you use tons of coroutines.

So does Java! Also, kotlinx.collections is still not stable and I don't think they are intending to make it so any time soon.

If you want to have O(1) with prepend you use the LinkedList. You get a lot of functional benefits but also all of the downsides like no random access. You can use the https://github.com/Kotlin/kotlinx.collections.immutable library to get O(log_64(n)). I haven't spent a ton of time on Tries so I might be a little wrong on that bound. BTW, these are persistent immutable data structures. At work, we use them inside of AtomicReference to roll our own Clojure Atoms.

This is why Kotlin refers to List as read-only, and not immutable, and has created a library for truly immutable collections: https://github.com/Kotlin/kotlinx.collections.immutable

What I know is only based on this discussion. It seems that pcollections is really outdated and should not be considered.

If you want true immutable collections, kotlinx.collections.immutable provides them. They will likely be integrated into the language eventually with value classes and better immutability support.

I could see this argument made with Clojure, but I don't really see what makes Scala significantly better at FP than Kotlin. Kotlin has an official persistent data structures library nowadays, and it's got lambdas and higher order functions.

It's not immutable, it's read-only, https://kotlinlang.org/docs/reference/collections-overview.html . I think that's a false assumption. But I get the point - immutable collections are not part of the std - for very good reasons. But we know each other, I assume that you will disagree :) For people who know what they want and know all the implications, there is https://github.com/Kotlin/kotlinx.collections.immutable .