-
Notifications
You must be signed in to change notification settings - Fork 8
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
WIP: Typelib loading #90
base: master
Are you sure you want to change the base?
Conversation
I dropped the ball on this. Sorry. Given the discussion occurring in #96 , is this still good to go? |
This is somewhat adjacent to #96, but can not solve it completely. I am not entirely sure, but I believe this solves a slightly different issue, wherein loading one typelib and creating all its definitions can leave you with an incomplete view on "the world" as defined through typelib dependencies. |
3c24848
to
366f9f9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apparently there's a really old review I ought to submit.
((module? module) module) | ||
((list? module) | ||
(let ((m (resolve-module module))) | ||
(set-module-duplicates-handlers! m %gig-duplicate-handlers) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Slight oversight, we should first check whether m is a fresh module.
This patch adds the immediate dependencies of a typelib to the module-uses of the module generated from it and installs a duplicate handler, which reports duplicates as Guile-GI warnings. We should try to resolve those at some point, and especially find out why our generics sometimes won't merge.