After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 734465 - GtkTreeModel iter_next and iter_previous should annotate iter as (inout)
GtkTreeModel iter_next and iter_previous should annotate iter as (inout)
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkTreeView
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtktreeview-bugs
gtktreeview-bugs
Depends on:
Blocks:
 
 
Reported: 2014-08-08 05:29 UTC by Simon Feltman
Modified: 2018-04-15 00:14 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Simon Feltman 2014-08-08 05:29:05 UTC
The iter argument is currently annotated as (in) (see [1]). This causes a problem for high-level languages which need to copy the boxed value when passing it as an argument to the vfunc. Currently this assumes pass-by-reference semantics which is not how high-level languages work with boxed types.

Unfortunately this cannot be fixed in the 3.x series without an API break because PyGObject currently suffers from bug 722899 which boxed types are passed by reference to vfuncs making the vfuncs noted here actually work (and we have programs relying on this chain of bugs).

This should be looked at for the 4.x series.

[1] https://git.gnome.org/browse/gtk+/tree/gtk/gtktreemodel.c?id=3.13.5#n1427
Comment 1 Matthias Clasen 2018-02-10 05:01:09 UTC
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 2 Matthias Clasen 2018-04-15 00:14:07 UTC
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new