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

infix path composition not parsed correctly #22

Open
mikeshulman opened this issue Jul 16, 2016 · 0 comments
Open

infix path composition not parsed correctly #22

mikeshulman opened this issue Jul 16, 2016 · 0 comments

Comments

@mikeshulman
Copy link
Contributor

I'm seeing some weird behavior with the current HoTT-Agda library in Agda 2.5.1.1: frequently when I want to compose two complicated paths, Agda is unwilling to parse the path-composition operator infix. It says complains something like

Don't know how to parse
(blah1)
∙ (blah2)
Could mean any one of
((blah1)
 ∙)
(blah2)
_∙_
(blah1)
(blah2)
Operators used in the grammar:
  ∙ (infixr operator, level 80) [_∙_ (/home/shulman/hott/agda/core/lib/PathGroupoid.agda:18,3-6)]
(the treatment of operators was changed in Agda 2.5.1, so code that
used to parse may have to be changed)

Here (blah1) and (blah2) are simple function applications, not mixfix operations, and both enclosed in parentheses, so I don't see what the ambiguity could possibly be. I haven't managed to isolate a MWE, but I wonder whether anyone else is seeing this? Is there an easy solution?

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

No branches or pull requests

1 participant