Give your opinion for the inclusion of new #scala collection operations http://bit.ly/2wVIMIy (https://goo.gl/forms/TWcrH81MoRppvXwN2 …)
-
It's a form delegating that decision to *you*. If you really think performance and new ops are mutually exclusive, say "no" to them all!
It's also basically impossible to, say, write "intersperse" efficiently by combining other ops. It would be welcome in the new collections.
-
-
Core problem is that collection operations cannot be efficiently combined. Adding more operations is addressing the symptom, not the issue.
-
I think it's orthogonal. With my example of intersperse, it's hard to write the function expressively in source from existing operations.
- Show replies
New conversation -
-
-
A problem perfectly demonstrated by the sprawling mess that is collections, iterators, views, parallel collections and Stream.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Addressing this was out-of-scoped right from the beginning of the new collection design, so it's not surprising that the flaws persist.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
It's "impossible" given the current design. That the flawed fundamentals are retained was a decision, not a necessity.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.