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 743094 - Convention for GVariant return value transfer annotations?
Convention for GVariant return value transfer annotations?
Status: RESOLVED DUPLICATE of bug 657202
Product: gobject-introspection
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gobject-introspection Maintainer(s)
gobject-introspection Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-01-17 16:22 UTC by Torsten Schoenfeld
Modified: 2018-01-24 19:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Torsten Schoenfeld 2015-01-17 16:22:06 UTC 
Is there a convention yet for transfer annotations of GVariant return values?  regress.c seems to use the same convention that is applied to GInitiallyUnowned, i.e. "transer none" for functions that return floating references: <https://git.gnome.org/browse/gobject-introspection/tree/tests/scanner/regress.c#n375>.  But gimarshallingtests.c  uses "transfer full": <https://git.gnome.org/browse/gobject-introspection/tree/tests/gimarshallingtests.c#n1719>.
Comment 1 Allison Karlitskaya (desrt) 2015-01-17 21:21:34 UTC 
I feel like this is at least a partial dup of bug 742618 (where I mention some specific thoughts about GVariant) and/or bug 657202.
Comment 2 André Klapper 2015-02-07 17:17:22 UTC 
[Mass-moving gobject-introspection tickets to its own Bugzilla product - see bug 708029. Mass-filter your bugmail for this message: introspection20150207 ]
Comment 3 Emmanuele Bassi (:ebassi) 2018-01-24 19:21:02 UTC 

*** This bug has been marked as a duplicate of bug 657202 ***