Previous: Compatibility, Up: Reference Guide [Contents][Index]
In most cases this is nothing to worry about. Guile-GI ensures, that
the core binding is used as the default behaviour when the signature
does not accidentally match that of a function in some typelib.
However, this can still cause issues when Guile-GI overrides syntax.
To protect your syntax (or other variables you deeply care about), use
the protect or protect* renamer from (gi util).
Most conflicts should be resolved using the merge-generics
duplicate handler. However, this handler is not enabled by default, so
you may want to push it to the default duplicate handlers. If this is
still not working, you may somehow have ended up with “equal”
duplicates, i.e. duplicates, whose bindings resolve to the same value.
To silence warnings about them, use the shrug-equals duplicate
handler defined in (gi util). If the conflict is still not
resolved, file a bug detailing it. As a workaround, you may also rename
either binding, which is probably the best way to resolve a duplicate.