The Coq mailing list

[Jason Gross <jasongross9 AT gmail.com>]

It is much worse than you realize.  [Reserved Notation]s cannot be undone except by restarting Coq.  This means that you are likely to be confused if you declare new notations in the middle of a file, back up past them, and change the notation; the parsing rules will still have the old notation baked into them.  Furthermore, it is often the case that [Require]ing a module without importing it is enough to break notations in various places.

-Jason

On Sat, Jun 7, 2014 at 9:11 PM, Chris Dams <chris.dams.nl AT gmail.com> wrote:

Hallo Jason and the rest,

Thank you for your suggestion, Jason. This solves the problem that I posted but it seems these levels also affect the priority that operators have and level 7 does not seem to be a very good idea for my operator. It should, for instance, not have precedence over + or *. So now I decided to not use ~ as an operator but to call it == instead. This seems to work. To me it seems very strange that a rather obscure operator binary concatenation operator defined somewhere in the libraries seems to make it quite unusable for other purposes. Couldn't there be a command to make coq forget about a particular notation definition so that an operator becomes freely usable again?

All the best,
Chris