Scala annoyance #27: … match { case x if someExpensiveCalc(x) => someExpensiveCalc(x) + foo } Expensive redundancy. :-(
-
-
Replying to @djspiewak
@djspiewak we need a lazy-val optimization for local blocks perhaps...4 replies 0 retweets 0 likes -
Replying to @jsuereth
@jsuereth@djspiewak No. This would be broken. It is *not* an optimisation. You can do explicit sharing (val) only.1 reply 0 retweets 0 likes -
Replying to @djspiewak
@djspiewak@jsuereth It is not an optimisation, it is a space/time trade that is not always optimal. See#haskell for this issue.3 replies 0 retweets 0 likes -
Replying to @dibblego1 reply 0 retweets 0 likes
Replying to @djspiewak
@djspiewak @jsuereth that does not make it optimal.
1:56 PM - 18 Sep 2012
0 replies
0 retweets
0 likes
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.