debox
debox copied to clipboard
non
Fast, deboxed, specialized data structures for Scala
This PR makes debox cross compile to Scala 2.13, updating dependencies as necessary and fixing breaking changes caused by the migration. With all changes, tests still pass and benchmarks still...
This mostly means that we now have an indirect dependency on cats 1.X instead of 0.9.X
It is mentioned in the README that there is a `##` operator for compute hashCode for the `Map`. 1) How does this interoperate with the default hashCode method? 2) If...
I don't know if it really is fast on the javascript side yet. Tests ran green without any effort, so that's pretty cool in itself
It seems that the main reason for the spire dependency is to provide basic typeclass instances so things work out of the box. None of the advanced features of spire...
a specialized immutable list might be of use. Likewise Vector and HashTrieMap/Set. Especially with concurrency, sometimes the immutable versions are better (when you need to provide snapshotting without copying).
debox.Map[Int, AnyRef].contains(key: Int) boxes, I do not know exactly why, but the performance suffers quite a bit:  This is on Scala 2.11.2. I wonder if it is the inner...
In analogy with [mutable.Map](http://www.scala-lang.org/api/current/index.html#scala.collection.mutable.Map@put%28key:A,value:B%29:Option[B]). Otherwise one has to search twice, with ``` scala val old = m.get(k) m.update(k, v) old ``` which, admittedly, is what `MapLike` does but isn't efficient....
This could be useful for building web applications with high performance. It looks like the Spire dependency would have to be cross-compiled for Scala.js first. I see there is already...
