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
On Fri, Jun 29, 2012 at 10:29 AM, Konrad Hinsen
wrote:
> What I worry about is not so much losing functionality, but
> restructuring of the code or renaming of the interfaces, functions,
> etc.
>
> Konrad.
I don't forsee the protocols or functions around logic vars &
unification changing. I'm act
> Of course all that machinery exists in core.logic and I think I
> identified most of it, but those interfaces don't look like they were
> meant to be used "from the outside". I certainly don't want to fix my
> code with every new release of core.logic. That's why I am looking
> for something more
David Nolen writes:
> It's important that core.logic be constructed on a solid set of lower
> level primitives. What functionality are you afraid of using from the
> outside?
What I worry about is not so much losing functionality, but
restructuring of the code or renaming of the interfaces, f
On Fri, Jun 29, 2012 at 9:37 AM, Konrad Hinsen
wrote:
> I wonder if there is any "official" (i.e. stable and ideally documented) way
> to use logic variables and unification from core.logic without running the
> constraint solver. More specifically, I'd like to
>
> - define some logic variables
>
