• Niels De Graef's avatar
    Don't pass default GLib marshallers for signals · 0314b482
    Niels De Graef authored
    By passing NULL to `g_signal_new` instead of a marshaller, GLib will
    actually internally optimize the signal (if the marshaller is available
    in GLib itself) by also setting the valist marshaller. This makes the
    signal emission a bit more performant than the regular marshalling,
    which still needs to box into `GValue` and call libffi in case of a
    generic marshaller.
    
    Note that for custom marshallers, one would use
    `g_signal_set_va_marshaller()` with the valist marshaller instead.
    0314b482
Name
Last commit
Last update
common @ 59cb6781 Loading commit data...
docs Loading commit data...
ext Loading commit data...
gst Loading commit data...
gst-libs Loading commit data...
hooks Loading commit data...
m4 Loading commit data...
pkgconfig Loading commit data...
po Loading commit data...
subprojects Loading commit data...
sys Loading commit data...
tests Loading commit data...
tools Loading commit data...
.gitignore Loading commit data...
.gitlab-ci.yml Loading commit data...
.gitmodules Loading commit data...
AUTHORS Loading commit data...
COPYING Loading commit data...
ChangeLog Loading commit data...
MAINTAINERS Loading commit data...
Makefile.am Loading commit data...
NEWS Loading commit data...
README Loading commit data...
README.static-linking Loading commit data...
RELEASE Loading commit data...
REQUIREMENTS Loading commit data...
autogen.sh Loading commit data...
configure.ac Loading commit data...
gst-plugins-base.doap Loading commit data...
meson.build Loading commit data...
meson_options.txt Loading commit data...