http://dev.clojure.org/jira This file is an XML representation of an issue en-us 4.4 649 25-07-2011 http://dev.clojure.org/jira/browse/LOGIC-68 core.logic <p>This can be done by annotating logic variables and embedding a run within a run by passing in the current substitution, running on it, and extracting out the reified values and unifying it back into the current substitution.</p> LOGIC-68

add Prolog meta-logical predicates bagof, setof, findall

Defect Major Open Unresolved David Nolen David Nolen Fri, 16 Nov 2012 13:20:26 -0600 Wed, 13 Feb 2013 13:50:21 -0600 0 1 <p>I'm working on understanding the answers given for this StackOverflow question:</p> <p><a href="http://stackoverflow.com/questions/7647758/prolog-findall-implementation">http://stackoverflow.com/questions/7647758/prolog-findall-implementation</a></p> <p>For discussion — Initial working patch supporting nested version of 'run-a/'run-a*. Binding symbols must match existing lvars with which vectors of all returned values will be unified.</p> <p>Should we provide wrappers that emulate each of bagof, setof and findall?</p> <p>I'm still not sold on the current names run-a/run-a*. "a" is really an internal implementation detail. Expect a revised patch with better names when I think of them (any ideas?).</p> <p>Yes please. Yeah I don't think the names of run-a/etc are critical - implementation details for now until we really understand the implications and it gets some use.</p> <p>I'm considering simply making <tt>run</tt>/<tt>run*</tt> conditionalized on the first argument, using the nesting form if we are being called with a substitution map as the first argument.</p> <p>My current understanding of <tt>bagof</tt> and <tt>findall</tt> makes me think they're not worth implementing beyond the nesting <tt>run</tt> functionality.</p> <p>I'm still thinking about <tt>setof</tt> which is quite useful and will want help from the infrastructure to be fully efficient.</p> <p>I'll submit a new patch after Thanksgiving.</p> <p>Excellent, thanks much.</p> <p>I have not forgotten, I've just gotten swamped.</p> <p>There's a small chance I'll get to this before Christmas, otherwise, it's after the new year.</p> <p>After a car accident, travel to London and Morocco, getting caught up at work and getting caught up on the apparently very busy stream of core.logic activity (great work!), I'm back on this.</p> <p>I found some bugs in my implementation after porting the patch forwards and realized these issues highlighted my sloppy understanding of some of the semantics I had created.</p> <p>I'm fairly convinced now that we don't want to name this after <tt>run</tt> or <tt>run*</tt>. It's too much of a strain to try to make it mean the same thing in a nested context.</p> <p>The current mechanism is still not quite a match for <tt>findall</tt>/<tt>bagof</tt>/<tt>setof</tt>, however, so I'm seeing what a good fit would be. I'll post meaningful thoughts for review as I have them.</p> <p>Glad to hear you're OK! No worries, will take a patch whenever you get around to one.</p> Global Rank