There might be a lot of code out there relying
on get_property() being Glib::Object::get_property(). I still think
that's broken, since there's no guarantee that subclasses avoid naming
methods "get_property".
Oh, well, you hope as a "social" matter when a subclass overrides it
does so in a kinda compatible way, so things you could do on the
superclass still have, mostly, the same result. There must be some oop
jargon for degrees of extending, narrowing, or whatnot of subclass
method semantics must there?