@travisbrown @huitseeker I often avoid for-comprehensions for exactly these kinds of reasons.
-
-
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 -
Replying to @eed3si9n
@eed3si9n@d6@huitseeker@travisbrown The final call to map, no type-safety, the filter nonsense...2 replies 0 retweets 1 like -
Replying to @dibblego
@dibblego@eed3si9n@d6@huitseeker@travisbrown I wasn't aware they were not type safe. Can you provide an example?1 reply 0 retweets 0 likes -
Replying to @coltfred
@coltfred@eed3si9n@d6@huitseeker@travisbrown Yeah but won't fit in a twittle.1 reply 0 retweets 0 likes -
Replying to @dibblego
@dibblego@eed3si9n@d6@huitseeker@travisbrown Mind constructing a gist when you have some time? I'm very interested.1 reply 0 retweets 0 likes -
Replying to @travisbrown
@travisbrown@coltfred@d6@dibblego@huitseeker Scala 2.10.2 returns `List(1): List[Any]`. Scala 2.10.0 throws scala.MatchError: 32 replies 0 retweets 0 likes
@eed3si9n @travisbrown @coltfred @d6 @huitseeker Scala Dunrite throws type error. Type-safe my arse!
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.