François Laignel

My plan was to start over from the PR you linked and implement the changes in the glib bindings. But I got involved with other stuffs. I'll try to resume...

Status on this: - [x] Rebased - [x] Started over from the commit from #1551 - [x] Added basic handling of the `zero-terminated` annotation. Note: I also considered handling `optional`...

@bilelmoussaoui: when you get a chance, I'd be interested by your opinion on the question in this comment https://github.com/gtk-rs/gir/pull/1622#issuecomment-2897061677

> can you open PRs for the changes for gtk4-rs/gtk-rs-core? i will review and merge this one afterwards. Done! * https://github.com/gtk-rs/gtk-rs-core/pull/1728 * https://github.com/gtk-rs/gtk4-rs/pull/2064

> Do we have example API somewhere with nullable array return values? * [`pango_font_face_list_sizes`](https://docs.gtk.org/Pango/vfunc.FontFace.list_sizes.html) * [`gdk_event_get_history`](https://docs.gtk.org/gdk4/method.Event.get_history.html) * [`gsk_stroke_get_dash`](https://docs.gtk.org/gsk4/method.Stroke.get_dash.html)

> Do we have examples of array returns that are _not_ nullable btw? Samples from `gtk-rs-core`: * [`gdk_pixbuf_save_to_buffer`](https://docs.gtk.org/gdk-pixbuf/method.Pixbuf.save_to_buffer.html) > Note that the buffer is not `NUL`-terminated and may contain embedded...

> Can you create an issue for that against gobject-introspection? https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/561 > Can you create an MR for that? https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4789

Resumed this. Had to implement new traits for the containers. Will perform a sanity check later as this was tedious and error prone.

> we would need the same treatment for the generated Builders as well :) Ah, that was deliberate, but I get your point! I'll look into this in a bit...

Builder generation updated.