Ah, that's the point I was making: My solution is to privilege neither and report ambiguities as an error.
Whoever caused the ambiguity is obliged to resolve it, and it's the person who wrote the first ```@dispatch``` on dispfu.
I think that's important. Making the ambiguities and the resolutions chosen explicit is important for making sure that everybody who reads the code understands all the subcases that are involved.