mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-09-09 09:28:44 +02:00
db96cb45ce
The identifiers and types in Gio-2.0 that are used for backward compatibility purposes in order to keep code importing Gio and using platform-specific API are actually breaking the platform-specific introspection data, because the introspection scanner favours types found inside dependencies as opposed to types with the same name found inside the current namespace. In practice, the backward compatibility hack of keeping duplicate types inside Gio-2.0 is effectively preventing people from using GioUnix-2.0 and GioWin32-2.0. We cannot change the introspection scanner, because that could have unforeseen results across the stack. We cannot remove the symbols and bump the namespace version of Gio and friends to 3.0, unless we keep generating known-to-be-broken 2.0 versions of all the namespaces. It also won't solve the issue of code loading Gio without specifying a version, because that always imples using the latest version of the namespace, which means backward compatibility would still need an explicit opt in. In practice, the only reasonable way forward is to break backward compatibility, and remove the duplicate symbols and identifiers from Gio-2.0, as we should have done in the first place. Fixes: #3744