Skip to content

Misleading "Precedence parsing error" when using an undefined operator

I was using QuickCheck and wrote something like this:

a > 0 ==> a == b

But I hadn't imported (==>), and I got an error about mixing two operators with the same fixity (the two comparisons). This error was misleading, since once I imported ==>, which has a lower fixity, there was no problem.

I have a complete example file to attach.

This might be identical to #2993 (closed), but the situation there was not quite the same, so I am filing a new bug rather than reopening it.

Trac metadata
Trac field Value
Version 7.6.3
Type Bug
TypeOfFailure OtherFailure
Priority normal
Resolution Unresolved
Component Compiler
Test case
Differential revisions
BlockedBy
Related
Blocking
CC ktvoelker@gmail.com
Operating system
Architecture
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information