Instead of writing, def fn() = { val result = someExpression doSomethingElse() result } I've found myself writing code like, def fn() = try someExpression finally doSomethingElse() more, even when `someExpression` is pure. I'm not entirely sure how I feel about it.
-
Clearly this is muuuuch better someExpression() :Id[X] <* doSomethingElse():Id[Y] On a slightly more serious note, I agree I'm not sure which is better but seing `try` immediatly get's my brain into "potentially failing" mode which might be misleading.
Yes, that was my feeling too. But thinking about it some more, I thought "but what if I'm wrong about it being pure?" and more often than not I concluded that my problems would be worse if an exception were thrown *and then* `doSomethingElse()` didn't happen.
-
-
I guess the question is central if doSomethingElse() is dependent on the assumption that the original expression is pure and always successful or is an actual finalizer of sorts?
Thanks. 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.