Recognize QML slots and register them as uses of their corresponding signal
Review Request #118596 - Created June 6, 2014 and submitted
It seems slightly backwards to first do the check for all queries and then filter out those where the match doesn't matter. What is the problem with a function which finds either foo or onFoo and which is only called in the places where you actually want that?
Review request changed
Don't extend findDeclaration() but introduce a new function, findDeclarationResolvingSignal (better name suggestions are welcome :) ). This avoids the overhead of the signal resolution when it is not needed (for QML base classes for instance, we never inherit from signals). UseBuilder still uses findDeclarationResolvingSignal because it doesn't know if the identifier for which it builds an use is a slot or not.
Revision 3 (+49 -2)