You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 1, 2020. It is now read-only.
Similarly, I get compile errors if I define an operator called =>. Is there a way to stop the syntax of my language from conflicting with the syntax of the meta-language? (I'm only up to the third tutorial video but I'm trying to play around with the concepts as they're introduced and I'm running into this problem already.)
=> is a reserved keyword for K. It is used in rules to specify rewriting rules.
K3.4 is quite old and had some issues regarding modularity but in K4 you can avoid these by splitting your syntax into different modules: 1. module for semantics, 2. module for program syntax 3. module for common syntax. The idea is to put all the productions that conflict with the builtin K stuff in the second module and keep the rest in the common module which you can include in both.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've just done the first tutorial video and I tried to compile this:
The causes an error:
However, if rename
"Type"
to something else...this compiles fine.
The text was updated successfully, but these errors were encountered: