Interesting. I understand that, I guess it's because of my usage of spec. I tend to use spec exclusively at the boundaries. Think serialization. Sometimes, I have a producer which can't handle the error, so it must be serialized and exchanged to the consumer.
So say the producer couldn't produce the value, for some reason. In some cases, that's a bug, and I throw an exception, and fail the producer itself. But sometimes, its an expected possibility, in which case, tbe value is an error. And the producer must communicate that out. Unfortunatly, exceptions are not friendly to serialization or spec. So I need to roll my own error structure, serialize that, and spec it. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
