The type system should have never been relegated to libgobject: it's a low
level API to register types at run time.
Having GType inside libglib allows us to use the type system information
everywhere:
- generic but type safe storage data types
- explicit memory management semantics for all data types
- enumeration types for all flags
Having the type system inside libglib also allows us to create new and
better fundamental types in the future, like sum types, option types,
tuples, and generic types.
Moved:
- gatomicarray
- gboxed
- genums
- gtype
- gtypeplugin
- gvalue
The move is mostly Git surgery, but given the amount of internal API
surface, it results in a single commit to avoid breaking bisectability.
We need to maintain `gobject/gvaluecollector.h` as a publicly installed
header but, to avoid issues in case of excessive inclusions, we make it
conflict with `glib/gvaluecollector.h`.
See: #2370
See: https://discourse.gnome.org/t/straw-man-moving-the-gtype-api-down-to-libglib-2-0/11169
This adds static markers and systemtap tapsets for:
* type creation
* object lifetimes (creation, ref, unref, dispose, finalize)
* signal creation and emission
Signal emissions and finalization marker have a corresponding
*_end (or *-end in dtrace) version that is when the corresponding
operation is finished.
https://bugzilla.gnome.org/show_bug.cgi?id=606044