My favourite hobby after @scalaworldconf is to read everything @edmund_noble writes on scala/scala gitter channel.
You should too#pure #gold
-
-
Replying to @EncodePanda @rabbitonweb and
His extreme views on whitespace should not be tolerated.
3 replies 0 retweets 7 likes -
Replying to @tpolecat @rabbitonweb and
Surely it's as extreme as
@djspiewak 's views on using '.' in Scala...1 reply 0 retweets 1 like -
I've actually significantly modified my views on '.' in Scala. A discussion with
@odersky was very compelling.1 reply 0 retweets 1 like -
-
Basically default to . and (...) for lambdas, but use space and { ... } if you need multi-line (including partial functions). Never post-fix
1 reply 0 retweets 5 likes -
Replying to @djspiewak @runT1ME and
I remember suddenly becoming comfortable with `foo { ... }.bar { ... }`-style chaining about four years ago, and it was quite liberating.
3 replies 0 retweets 0 likes -
Replying to @propensive @runT1ME and
I've always been uncomfortable with that. Unfortunately, `foo { }.bar { }` has different type inference than `foo { } bar { }`.
1 reply 0 retweets 0 likes
This is why `match` bugs me, now. I'd love to be able to write `value.match { ... }.map { ... }`, like I could back in Scala 1.x... ;)
-
-
Replying to @propensive @djspiewak and
You may not be able exactly but you could define a match method and wrap it into an implicit class.
0 replies 0 retweets 1 likeThanks. 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.