Permalink
Commits on Mar 29, 2013
  1. [maven-release-plugin] prepare release core.logic-0.8.3

    Hudson @ build.clojure.org committed Mar 29, 2013
  2. 0.8.3

    swannodette committed Mar 29, 2013
  3. LOGIC-126: bad fd/* fd/+ from StackOverflow

    swannodette committed Mar 29, 2013
    The issue is that it's possible for a var to have both a value and
    domain. Previously get-dom *always* returned the domain, this
    permitted an the undesirable situation that constraints checked against
    the domain and not the actual value.
    
    Now the fundamental get-dom always return the value if the var has one
    over the domain (it continues to return nil in the unfound case, which
    will likely change). After auditing the fd code it's clear that the
    primary use of get-dom was the desire to get the actual value or the
    domain. The only place where we don't do this is domc. domc has to
    reach into the implementation. This is OK for now, I'd like to see
    how CLP(Set) and other constraint domains play out.
    
    We tweaked resolve-storable-dom in the singleton case. We only run
    constraints if the var doesn't have a binding (we wouldn't have made
    it this far if it had). This prevents I believe the bad behavior we
    seen in the past when flipping walk/get-dom in let-dom.
    
    let-dom now just uses get-dom, no separate walk. Added note in
    distintc why we need both get-dom and walk there.
    
    Overall we're getting closer, but I think further simplifications and
    improvment can be made.
Commits on Mar 26, 2013
  1. tweak

    swannodette committed Mar 26, 2013
  2. [maven-release-plugin] prepare for next development iteration

    Hudson @ build.clojure.org committed Mar 26, 2013
  3. [maven-release-plugin] prepare release core.logic-0.8.2

    Hudson @ build.clojure.org committed Mar 26, 2013
  4. 0.8.2

    swannodette committed Mar 26, 2013
Commits on Mar 24, 2013
  1. remove stale comments

    swannodette committed Mar 24, 2013
  2. LOGIC-124: fix disjoint?* bug uncovered by Ryan Senior's test

    swannodette committed Mar 24, 2013
    case. Add additional disjoint tests.
Commits on Mar 18, 2013
  1. add some missing changes

    swannodette committed Mar 18, 2013
  2. [maven-release-plugin] prepare for next development iteration

    Hudson @ build.clojure.org committed Mar 18, 2013
  3. [maven-release-plugin] prepare release core.logic-0.8.1

    Hudson @ build.clojure.org committed Mar 18, 2013
  4. 0.8.1

    swannodette committed Mar 18, 2013
  5. LOGIC-108: recursive featurec. Add protocol IFeature. Implementers

    swannodette committed Mar 18, 2013
    should return something which can optional unify in the manner of
    partial-map. Extend IPersistentHashMap to IFeature. Add test cases
    demonstrating recursive behavior.
  6. LOGIC-83: fix typo in test

    swannodette committed Mar 18, 2013
Commits on Mar 17, 2013
  1. LOGIC-71: fixed unifier reify vars issue some time ago. Documenting

    David Nolen committed Mar 17, 2013
    the fix with a test.
  2. LOGIC-116: In `migrate` the root may not have an entry in `km`, we

    David Nolen committed Mar 17, 2013
    need to return the empty set in that case, otherwise will we'll call
    into on nil which defaults to a seq causing the set only operations
    like `disj` to fail.
  3. Merge branch 'master' of github.com:clojure/core.logic

    David Nolen committed Mar 17, 2013
  4. walk-term for ISeqs should not be lazy, refs #121

    jonase committed with David Nolen Mar 16, 2013
    Attach metadata only to terms that support it, refs #120
    
    lvars-store should be a map and not a set, refs #122
    
    Tests for LOGIC-120, LOGIC-121 and LOGIC-122
  5. [maven-release-plugin] prepare for next development iteration

    Hudson @ build.clojure.org committed Mar 17, 2013
  6. [maven-release-plugin] prepare release core.logic-0.8.0

    Hudson @ build.clojure.org committed Mar 17, 2013
  7. 0.8.0

    David Nolen committed Mar 17, 2013
Commits on Mar 13, 2013
  1. [maven-release-plugin] prepare for next development iteration

    Hudson @ build.clojure.org committed Mar 13, 2013
  2. [maven-release-plugin] prepare release core.logic-0.8.0-rc3

    Hudson @ build.clojure.org committed Mar 13, 2013
  3. bump version

    swannodette committed Mar 13, 2013
  4. include 112 test case

    swannodette committed Mar 13, 2013
  5. optimization

    swannodette committed Mar 13, 2013
  6. LOGIC-112: Incorrect results with tabled resolution

    swannodette committed Mar 13, 2013
    The bug was introduced when we switched the answer cache to sets. In
    `reuse` we were calling `first` on the set which of course won't
    work.
    
    We not have an `AnswerCache` type. This holds both the list of answers
    for determining the fixpoint as well as the answers as a set for
    quickly determining whether we've already cached an answer.
    
    The additionally memory overhead does make it desirable to have more
    sharing of tabled information between answer caches.
Commits on Mar 12, 2013
  1. first pass at new table cache type. nondeterminism and general bad

    swannodette committed Mar 12, 2013
    behavior in tabling results from the `(first ansv*)` line in the
    implementation of `reuse` - there's no guarantee what that will return
    for sets. Ooops.