although I like it, it's not really the standard way to interact with glib signals in rust. maybe lock it behind an experimental flag, though if it already has its own feature so that should be fine on its own. Make sure to doc(cfg()) it!
[x] feature flag it, with enable-glib-signal or something
[x] release glib-signal to crates.io (otherwise it can't be referenced as a dependency at all)
although I like it, it's not really the standard way to interact with glib signals in rust. maybe lock it behind an
experimentalflag, though if it already has its own feature so that should be fine on its own. Make sure todoc(cfg())it!enable-glib-signalor somethingglib-signalto crates.io (otherwise it can't be referenced as a dependency at all)