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

Decomplect unification in explanations #3

Open
alex-dixon opened this issue Oct 25, 2017 · 1 comment
Open

Decomplect unification in explanations #3

alex-dixon opened this issue Oct 25, 2017 · 1 comment

Comments

@alex-dixon
Copy link
Contributor

We should disambiguate between a constraint that merely "gets" or captures a value vs. one that is an equality constraint.

Then an explanation can be less ambiguous:
where <entityid, attribute, value> is <a literal value or an already bound ?variable>
bind to <first referenced ?variable / unbound ?variable>

Without the distinction we use something like "where" for the capture, which doesn't fit.

Second references to bound variables should use "where" as we are then talking about equality.

@alex-dixon
Copy link
Contributor Author

This analysis is useful if we add plain English explanations back. This was before we imported our entire syntax :)

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

No branches or pull requests

1 participant