3 ms·
That's eons ago in Scala world. If you can, give it another try. I would assume such a bug was fixed in Scala 2.x given the prevalence of the language in the h
by hocuspocus 4y ago
That's eons ago in Scala world. If you can, give it another try.
I would assume such a bug was fixed in Scala 2.x given the prevalence of the language in the hadoop ecosystem and big data frameworks.
Moreover Scala 3, was the opportunity to fix many previously-unfixable corner cases.