Recursive name and nametype definitions #28
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello! As we discussed, I added support for recursive name and nametype definitions by (co)induction on the session index, and now a session index has an additional natural number like structure.
Examples:
More examples can be found in
tests/success/recursive_name.owl.All current test cases are passing.
Some potential issues:
subNameType. I made it so that we don't unfold recursive name types initially innormalizeNameType, but instead unfold as needed when we actually comparing two types insubNameType. But I'm not completely sure if that interacts with other types well.Thanks in advance for any comments!