I'm curious about this stuff too. (I'm very new to Clojure.) I wouldn't be surprised if the general sentiment is: “Don't.”
The argument goes along these lines: By encapsulating, you have introduced a tiny new little API that clients need to learn the semantics of. Additionally, that API is likely not amenable to the plethora of other functions available in the standard library that are designed to work against a compact set of abstractions. Part of me is with you, though, and I'm curious if there are patterns that let you encapsulate in a way that works out cleanly. -- 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.
