-
-
Notifications
You must be signed in to change notification settings - Fork 172
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
Shift context judgement #367
Comments
@joneshf: Oh, whoops. That is a mistake on my part. I'll change it to use |
Gabriella439
added a commit
that referenced
this issue
Feb 12, 2019
Fixes #367 The judgment mistakenly implies that the variable being shifted must match each variable in the context. This fixes the judgment to use different variable names to avoid confusion.
Fix is up here: #369 |
Gabriella439
added a commit
that referenced
this issue
Feb 22, 2019
Fixes #367 The judgment mistakenly implies that the variable being shifted must match each variable in the context. This fixes the judgment to use different variable names to avoid confusion.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was reading through the semantics and ran into something that I need clarification on. In the shift context section, there are two judgements:
Should there also be a judgement for the case where the variable does not match?
The text was updated successfully, but these errors were encountered: