Skip to content
Commit c0740446 authored by Daniel Drake's avatar Daniel Drake Committed by Martin Pitt
Browse files

Optimize signal lookup in gi repository

Now that we have GSignalQuery results available to us when connecting
signals, we already know which GType implements the signal in question.

Therefore there is no need to traverse the class parent hierarchy
looking for this, which takes a considerable amount of CPU time.

There is also no need to canonicalize the signal name; both before
and after this patch, by the time we reach this point we have already
successfully looked up the signal name as presented from Python.

https://bugzilla.gnome.org/show_bug.cgi?id=696143
parent e220706b
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment