[BUGFIX] Fixing DAS vars resolution #729
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rationale
While working with MeTTa and DAS Gate, I faced the following situation: the same query that works perfectly with the built-in atom space, when executed using DAS, does not resolve some variables if a function is defined and called to match some condition.
For example:
The first line is the output of a query on DAS. And the second one comes from the same query but using the built-in space.
The issue does not happen on DAS if the match is made without calling a function.
For example, this query fails (output shows a non-resolved variable):
However, this
match
works perfectly (it shows the value):And both queries are equivalent.
Sample Script
(two first queries do not have variables properly resolved)
Output is:
(two first lines should show
John
instead of$y#40
and$y#55
)Vitaly's feedback on Mattermost