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

WOQL instantiation errors should return the bound variable name #77

Open
GavinMendelGleason opened this issue Dec 12, 2019 · 0 comments
Labels
bug Something isn't working

Comments

@GavinMendelGleason
Copy link
Member

Currently we get a rather uninformative error message referring to an internal unbound prolog variable. We need to do a backwards lookup in the environment and report this instead. This could be a bit tricky as we need to catch in a context in which the environment is exposed to us. Potentially we need to do a re-throw wrapper around the entire prolog term compiled so that we can ensure this.

@GavinMendelGleason GavinMendelGleason added the bug Something isn't working label Oct 1, 2020
@matko matko added the core label Mar 5, 2021
@matko matko added this to actual-triage in Core dev (old) Mar 5, 2021
@matko matko moved this from triage to Later in Core dev (old) Mar 8, 2021
@matko matko removed the core label Mar 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Development

No branches or pull requests

2 participants