On Thu, Mar 15, 2012 at 3:08 PM, Sean Corfield <seancorfi...@gmail.com>wrote:
> In other words, you want access to both unqualified cons and conso, > rest and resto etc in the same code? Yet core.logic overrides == and > so you either have to namespace that or exclude it (the examples seem > to do the latter) which seems to run counter to that. It's not a big > deal. It's just a bit jarring when you first start using core.logic > (which is a very cool library BTW). It has nothing to do w/ qualified or not qualified, namespaces or anything else. In some programs you may want to freely mix functions and relations. Tacking on an o is a simple convention to easily differentiate relations from normal functions. Take it or leave it :) David -- 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
