Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Post search results to an AnchorLink #2500

Merged
merged 11 commits into from
Feb 10, 2020
Merged

Post search results to an AnchorLink #2500

merged 11 commits into from
Feb 10, 2020

Conversation

linas
Copy link
Member

@linas linas commented Feb 10, 2020

This is a partial, initial-draft solution to issue #1502 - it allows results
to be posted to an AnchorLink, instead of returning them in a SetLink.
The changes to enable this are small, and the example is easy.

@linas linas merged commit 46dea8e into opencog:master Feb 10, 2020
@linas linas deleted the anchor-link branch February 10, 2020 04:07
linas added a commit to linas/atomspace that referenced this pull request Dec 16, 2022
Linking results to the AnchorNode idea now seems like a bad idea,
in retrospect.  The ideas in opencog#2911 seem superior. So trash the
AnchorNode support in the query subsystem.

FWIW, if this kind of thing was wanted, a better solution would
be a new kind of Value, that dequeued from a QueueValue, and
plopped the results onto an AnchorNode. ***This*** is the real
reason for stripping away this code: its not generic enough.

This reverts commit 46dea8e, reversing
changes made to 5ec84bb.
linas added a commit that referenced this pull request Dec 16, 2022
Linking results to the AnchorNode idea now seems like a bad idea,
in retrospect.  The ideas in #2911 seem superior. So trash the
AnchorNode support in the query subsystem.

FWIW, if this kind of thing was wanted, a better solution would
be a new kind of Value, that dequeued from a QueueValue, and
plopped the results onto an AnchorNode. ***This*** is the real
reason for stripping away this code: its not generic enough.

Merge branch 'revert-anchor'
@linas
Copy link
Member Author

linas commented Dec 16, 2022

This pull req was reverted in eee7a61

Basically, it just seemed like a bad idea, in the end.

FWIW, if this kind of thing was wanted, a better solution would
be a new kind of Value, that dequeued from a QueueValue, and
plopped the results onto an AnchorNode. This is the real
reason for stripping away this code: its not generic enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant