Michael Fogus writes: > It's not a total solution to all of your requirements, but core.unify > is meant for use as a library. See > https://github.com/fogus/unifycle/blob/master/src/fogus/unifycle.clj > for examples.
Looks interesting, but I do need logic variables as distinct entities that can be created and then submitted to constraints by unification. In fact, what I want to do is use logic variables for dataflow programming. The main point of building on top of core.logic would be to avoid rewriting a unification engine that handles logic variables also inside (potentially nested) data structures. David Nolen writes: > I don't forsee the protocols or functions around logic vars & > unification changing. I'm actually quite happy with how flexible & > extensible it's turned out to be. cKanren is just around the corner > and unification has been left alone. That sounds promising indeed. Konrad. -- 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
