Work on inference, unification and subject-reduction#328
Work on inference, unification and subject-reduction#328rlepigre merged 71 commits intoDeducteam:masterfrom
Conversation
|
There is a bug I need to fix. I am working on it. |
… that are non-linear or appears in the RHS as it may change after SR
…g RHS typing constraints
|
I have a question: do we assume somewhere in the code that a meta of arity n has a type of the form \forall x1:A1,..,\forall xn:An,B? |
I'm not sure, but most probably. |
rlepigre
left a comment
There was a problem hiding this comment.
There are still changes in there that I think are a mistake, but I guess I can live with them.
|
So can I merge @fblanqui? (I want to do it myself because I want to fix the commit message.) |
|
I have a question: do you keep the LHS unchanged after scoping? |
For now yes, but it will have to change once I implement the optimisation. |
|
Ok. The optimisation does not change the matching behavior. It is important to not change this indeed. Only the RHS metavariables should be instantiated by something. |
|
Thanks to merge @rlepigre . And thanks for your improvements on this PR! |
Yeah, the only thing that the optimisation will do is just not record the term matching a pattern variable in the case where it is not useful in the RHS (and does not appear non-linearly). This means that we will have wildcards again (i.e., terms of the form |
fix type inference, unification, handling of implicit arguments in rules, subject-reduction
fix issues #303 #330 #334