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

TODO: parser validity checks #6

Open
tnelson opened this issue Sep 5, 2013 · 3 comments
Open

TODO: parser validity checks #6

tnelson opened this issue Sep 5, 2013 · 3 comments

Comments

@tnelson
Copy link
Owner

tnelson commented Sep 5, 2013

Using this issue as a TODO list for parser checks.

  • If a TField appears with an unused variable name, error.
  • If a TField appears with an invalid field, error.
  • All relations used must be declared either remote or local.
  • No overlap between local/remote/inc/out relations
@tnelson
Copy link
Owner Author

tnelson commented Sep 5, 2013

Arity mismatches between table use and table declaration. (This WILL cause +/- rules to be ignored otherwise!)

@tnelson
Copy link
Owner Author

tnelson commented Sep 8, 2013

Any head vars that don't appear in body, including fields.

This is a controversial language choice, since it involves deciding whether every field needs to be explicitly constrained in rules...

@tnelson
Copy link
Owner Author

tnelson commented Sep 11, 2013

If attempting to modify new.locSw in a forward rule, should be an automatic parser failure.

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

No branches or pull requests

1 participant