-
-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for dynamic types #55
Comments
What's your use-case? |
Subclassing 😔 In my particular case, things go sideways when you call |
For usage with a specific library or ...? But if you have any suggestions how that could look like API-wise that would be useful. I'm mostly worried about the safety aspects here (unloading code is unsafe), that needs some thinking. Apart from that this should in theory only require adding bindings for |
That should only return |
It does return NULL. Alas, it's a part of a [proprietary] system that uses that object for further introspection on the loaded library (namely, plucking out some exported symbols). It's something that can be worked around, but full support obviously isn't quite there yet. |
Apart from the safety aspects this shouldn't be too hard to implement in any case, see above if you're interested in working on that :) |
Quite possibly, but I'm still a Rust novice, so it might be a bit 😉 |
Sure, feel free to ask here if you need some help :) |
See #1169 |
glib_wrapper! doesn't appear to have any support for dynamic types (types that become available after being loaded from a dynamic library)
https://developer.gnome.org/gobject/2.64/GTypeModule.html#G-DEFINE-DYNAMIC-TYPE:CAPS
The text was updated successfully, but these errors were encountered: