Undefined behavior when adding an iterator that conflicts with existing iterators

There are two ways for an iterator configuration to conflict with the existing configuration: in the distinguishing name of the iterator, and in the priority of the iterator. I propose throwing an exception when either of these conflicts occurs, allowing the user to remove the conflicting iterators or to change the configuration of the new iterator, then to try again.