Thanks to @huitseeker for the answer, but the fact that `for ((_,_)<-List(1->2))()` needs a filter still seems crazy: http://stackoverflow.com/a/17427067/334519 …
-
-
Replying to @travisbrown
@travisbrown@huitseeker I often avoid for-comprehensions for exactly these kinds of reasons.2 replies 0 retweets 0 likes -
Replying to @d6
.
@d6@huitseeker@travisbrown should the takeaway be avoid for-comprehensions, avoid tuples, or avoid matching on parameterized types?2 replies 0 retweets 0 likes -
Replying to @eed3si9n
@eed3si9n@d6@huitseeker@travisbrown avoid for-comprehensions almost always. Another thing#scala continues to get wrong.2 replies 0 retweets 1 like -
Replying to @dibblego
@dibblego@d6@huitseeker@travisbrown because the semantics is not clear? didn't know `for` was so controversial2 replies 0 retweets 0 likes
@eed3si9n @d6 @huitseeker @travisbrown #scala for-comprehensions get a lot of little things wrong that usually sum up to give you a bad day
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.