-
Notifications
You must be signed in to change notification settings - Fork 6
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
Type-check expressions #87
Projects
Comments
treiher
added a commit
that referenced
this issue
Sep 11, 2020
treiher
added a commit
that referenced
this issue
Sep 11, 2020
treiher
added a commit
that referenced
this issue
Sep 11, 2020
Preserve the locations of expressions during substitution and enable the substitution of an entire expression, if not already supported. Ref. #87
treiher
added a commit
that referenced
this issue
Sep 11, 2020
treiher
added a commit
that referenced
this issue
Sep 11, 2020
treiher
added a commit
that referenced
this issue
Sep 11, 2020
treiher
added a commit
that referenced
this issue
Sep 11, 2020
Preserve the locations of expressions during substitution and enable the substitution of an entire expression, if not already supported. Ref. #87
treiher
added a commit
that referenced
this issue
Sep 11, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we do not check whether variables and literals used in expressions fit together at the specification level. Consequently, some type mismatches cannot be detected, e.g. when comparing a field of one enumeration type to a literal to a different, incompatible enumeration type. To fix this, we need to implement type inference for expressions.
The text was updated successfully, but these errors were encountered: