Parse error on double implications
!x: Largest(x) => Largest(x) => Largest(x). throws a parse error on the second =>
Comments (6)
-
reporter -
reporter - marked as minor
- marked as enhancement
-
-
assigned issue to
-
assigned issue to
-
- changed status to resolved
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>>
-
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>>
-
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>>
- Log in to comment
This is not a bug, but it would be useful to have a better warning that in fact the sentence is ambiguous without brackets.