core.logic

Allow retraction of previously stated facts in a relation

Details

  • Type: Enhancement Enhancement
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Completed
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
  • Patch:
    Code and Test

Description

For long-running or interactive programs, it is useful to allow facts to become "no longer" true at a point in time.

Attachments

  1. Text File
    relational-retraction.patch
    18/Jan/12 12:42 PM
    5 kB
    Michael Nygard
  2. Text File
    relational-retraction.patch
    13/Jan/12 1:42 PM
    3 kB
    Michael Nygard
  3. Text File
    relational-retraction.patch
    11/Jan/12 7:10 AM
    2 kB
    Michael Nygard

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Michael Nygard added a comment -

I've found a bug in this patch. It doesn't handle indexes correctly. New patch coming soon.

Show
Michael Nygard added a comment - I've found a bug in this patch. It doesn't handle indexes correctly. New patch coming soon.
Hide
Permalink
Michael Nygard added a comment -

New patch that correctly updates indexes when retracting facts.

Show
Michael Nygard added a comment - New patch that correctly updates indexes when retracting facts.
Hide
Permalink
David Nolen added a comment -

This looks good but could we get a properly formatted patch w/ attribution information? Thanks!

Show
David Nolen added a comment - This looks good but could we get a properly formatted patch w/ attribution information? Thanks!
Hide
Permalink
Michael Nygard added a comment -

Happy to. What needs to be different for the patch to work? Also, what attribution are you looking for? Author info in the function?

Show
Michael Nygard added a comment - Happy to. What needs to be different for the patch to work? Also, what attribution are you looking for? Author info in the function?
Hide
Permalink
David Nolen added a comment -

Did you make the patch with git? Git should add that information.

Show
David Nolen added a comment - Did you make the patch with git? Git should add that information.
Hide
Permalink
Michael Nygard added a comment -

I did make the patch with git.

Show
Michael Nygard added a comment - I did make the patch with git.
Hide
Permalink
David Nolen added a comment -

Normally git patches I've applied have a header like the following:

From 8a44aec861c91a9652f3d60093d3d556a490067e Mon Sep 17 00:00:00 2001
From: Bobby Calderwood <bobby_calderwood@mac.com>
Date: Fri, 13 Jan 2012 09:24:29 -0500
Subject: [PATCH] MultiFn implements IHash

How exactly are you creating the patch with git?

Show
David Nolen added a comment - Normally git patches I've applied have a header like the following: 
From 8a44aec861c91a9652f3d60093d3d556a490067e Mon Sep 17 00:00:00 2001
From: Bobby Calderwood <bobby_calderwood@mac.com>
Date: Fri, 13 Jan 2012 09:24:29 -0500
Subject: [PATCH] MultiFn implements IHash
How exactly are you creating the patch with git?
Hide
Permalink
Michael Nygard added a comment -

I had been using git diff. New patch file attached using git format-patch. I think this is what you're looking for.

Show
Michael Nygard added a comment - I had been using git diff. New patch file attached using git format-patch. I think this is what you're looking for.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4#649-r158309) | Report a problem
Powered by a free Atlassian JIRA open source license for Clojure. Try JIRA - bug tracking software for your team.