-
Notifications
You must be signed in to change notification settings - Fork 0
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
Legacy terms #5
Comments
A similar point could be made for rewrite rules: The draft currently states "Legacy Dedukti syntax" under that point, but the BNF allows something like |
I think the old syntax should be what is, the syntax of the |
The lambda is the notation (given by the latex package) for the empty production. |
Do not worry about Kontroli, it accepts precisely what you described as rewrite rule contexts, namely But you are only talking about what the old syntax should be. Should the new syntax diverge from this in your opinion? |
The current standard draft gives a grammar for so-called "legacy terms" as follows:
(See, by the way, how having even BNF as Markdown would make discussion easier? We could just copy-paste parts of the Dedukti standard here and have it syntax-highlighted in discussions. ^^)
Now these "legacy terms" are not what is described in syntax.bnf. In particular, the syntax for lambda-abstractions and dependent products diverges. However, my intuition thinks that "legacy" describes something that "is already there", in other words, the "state of the art". I therefore find the current wording a bit misleading.
Are the differences between the terms in syntax.bnf and the "legacy terms" described in the draft on purpose? If so, what is the reason for the differences?
The text was updated successfully, but these errors were encountered: