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

Higher-Order rules : documentation #60

Closed
francoisthire opened this issue Aug 24, 2018 · 5 comments
Closed

Higher-Order rules : documentation #60

francoisthire opened this issue Aug 24, 2018 · 5 comments

Comments

@francoisthire
Copy link
Contributor

Trying to test lambdapi on example #59 , I found that documentation was missing for HO rules.

I have the impression that the correct syntax (right now) is:

A : Type.

a : A.

def f : (A -> A) -> A.

f (x => ?y[x]) --> a.

However, the following syntax is rejected not at parsing level (btw the error message could be improved):

(; KO 9 ;)

A : Type.

a : A.

def f : (A -> A) -> A.

[y] f (x => ?y[x]) --> a.

While the example below is rejected at parsing level:

A : Type.

a : A.

def f : (A -> A) -> A.

[y] f (x => y[x]) --> a.

At least we should have a note that explain the differences between the syntax of Dedukti and the one of lambdapi.

@rlepigre
Copy link
Contributor

Well, you should not be able to mix the legacy syntax with the actual lambdapi syntax. I'll check what I can do to reject the last two examples, and document the syntax properly.

@rlepigre
Copy link
Contributor

rlepigre commented Sep 6, 2018

There is no bug here (any more?), only missing documentation. The first example uses the (correct) new syntax. The second example attempts to mix legacy syntax with new syntax, which is rejected at scoping type with an adequate error message (pointing to the position of the ?y[x] subterm). Finally, the last example is simply not syntactically correct: y[x] has no meaning in either the legacy and the new syntax.

@rlepigre rlepigre removed the bug label Sep 6, 2018
@francoisthire
Copy link
Contributor Author

Maybe the file "newRuleSyntax.dk" should be renamed so that it is easier to understand that it is about Higher-Order patterns.

@fblanqui
Copy link
Member

@rlepigre : can't we close this issue?

@rlepigre
Copy link
Contributor

@fblanqui: I guess so.

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

No branches or pull requests

3 participants