Hi,
I don't like the behavior, either. However, type priorities were
introduced because of user requirements. They're certainly not
an implementation convenience. Quite the opposite, in fact :-)
Now if enough users speak up, maybe we can change something.
Perhaps by default, type priorities should not be used and
you'd need to do something special to activate them. One
might imagine special iterator overloads that respect type
priorities.
yes, I think thats very a good idea.
The problem that type priorities are trying to address is
a valid one, IMHO. I'm just not sure that the way we're
tackling this is the best one.
IMHO its a little bit unintuitive that by default the subiterator uses
the priorities in this way: I would just not have expected that when two
types have the same spans and one has inferior priority, the subiterator
would not return me this type.
Katrin
