-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Make applyo
use constraints
#19
Comments
There are some ambiguities regarding when/how a term should be constructed by the aforementioned constraint, and that leads me to believe that an entirely different goal should be designated to this function, and that |
is this still relevant since there is applyo? |
Yes, |
buildo
(soon to be replaced byapplyo
) will actually apply a rator to its rands and unify the result with its third argument: i.e.buildo(add, (1, 1), q_lv)
should unifyq_lv
with3
.We need to use the new constraint system to make sure that, for example,
add(1, 1)
is computed and unified withq_lv
oncerator_lv
andrands_lv
are fully ground in a goal likebuildo(rator_lv, rands_lv, q_lv)
.The text was updated successfully, but these errors were encountered: