If we're throwing errors at runtime then we're no better than the animals.
-
suggestion: If it's error free: f:`[X]X=>A`, if not g:`[X]=>Err \/ A`. lift f to combine/compose it f. that makes the "dragging much" easier, and keeps everything honest.
There is some pain to describe, if you are using scala, but you cannot express lenses and prisms accurately. You'll get that same pain with exceptions though.
-
-
with throwing exceptions? This pain is much much bigger, and even bigger if the exception is meant to be caught.
-
Yes, I am just saying, there is a way to make the original statement correct. But it is a stretch; an extreme stretch. There is no pain with data types done and used responsibly. Even given Scala.
End of conversation
New conversation -
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.