Parse error on double implications

Issue #278 resolved
Broes De Cat created an issue

!x: Largest(x) => Largest(x) => Largest(x). throws a parse error on the second =>

Comments (6)

  1. Broes De Cat reporter

    This is not a bug, but it would be useful to have a better warning that in fact the sentence is ambiguous without brackets.

  2. Bart Bogaerts

    Fixed double implications.

    Double implications are now parsed as right associative, as is common in first-order logic. I updated the documentation to include this knowledge. Also added a test for this parsing. This fixes #278

    → <<cset 5dffec8f4a83>>

  3. Bart Bogaerts

    Fixed double implications.

    Double implications are now parsed as right associative, as is common in first-order logic. I updated the documentation to include this knowledge. Also added a test for this parsing. This fixes #278

    → <<cset bc66683b3e9a>>

  4. Bart Bogaerts

    Fixed double implications.

    Double implications are now parsed as right associative, as is common in first-order logic. I updated the documentation to include this knowledge. Also added a test for this parsing. This fixes #278

    → <<cset 5a188a32bfc7>>

  5. Log in to comment