You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since #3511 has been fixed, I have a proposal to enhance the methods zip&zipped in Tupel2(Tuple3). As we known, we can use (xs,ys).zip and (xs,ys).zipped in Scala2.8 where xs and ys are both some type of Traversable. There are some limited in current implementation.
Let
@paulp said:
(In r23384) Some issues with Tuple2/3. There was a stray wrong-arity
foreach method in Tuple3, and both classes have what is now
a redundant zip method which is also unfortunately completely
strict in a not entirely fixable fashion. So "zip" is
deprecated in favor of zipped. Closes #3526, but the code
which closes that is primarily found in r23228. No review.
Since #3511 has been fixed, I have a proposal to enhance the methods zip&zipped in Tupel2(Tuple3). As we known, we can use (xs,ys).zip and (xs,ys).zipped in Scala2.8 where xs and ys are both some type of Traversable. There are some limited in current implementation.
Let
,then the following codes are invalid:
While I expected:
Here is my proposal which could fix these shortages:
Similar changes should be made in Tuple2#Zipped#{map,flatMap,filter}, Tuple3#zip and Tuple3#Zipped#{map,flatMap,filter}.
The effection:
Note: I think that this proposal doesn't fix #2634, since there is some problems of Stream#iterator(see #3273).
The text was updated successfully, but these errors were encountered: