Give your opinion for the inclusion of new #scala collection operations http://bit.ly/2wVIMIy (https://goo.gl/forms/TWcrH81MoRppvXwN2 …)
-
-
Replying to @etorreborre
Instead of fixing the performance issues with collections,
#Scala decides to just add new methods combining multiple existing ones? Sad.1 reply 0 retweets 1 like -
Replying to @oxnrtr @etorreborre
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!
1 reply 0 retweets 1 like -
It's also basically impossible to, say, write "intersperse" efficiently by combining other ops. It would be welcome in the new collections.
4 replies 0 retweets 0 likes -
Replying to @propensive @etorreborre
Core problem is that collection operations cannot be efficiently combined. Adding more operations is addressing the symptom, not the issue.
1 reply 0 retweets 0 likes -
Replying to @oxnrtr @etorreborre
I think it's orthogonal. With my example of intersperse, it's hard to write the function expressively in source from existing operations.
2 replies 0 retweets 0 likes -
And yet it's a common operation which I find myself writing many times a year.
2 replies 0 retweets 0 likes
I know you feel that people don't listen to you, but it seems like all your input these days is phrased based on the predicate they won't.
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.