No subject

d by
a modification of the returned value. It's always to iterate over it, like
foreach (account in am.get_valid_accounts()){}.

otoh, refcounted structs are cheap to dup, strings are safe to return as co=
nst,
and collections are always small (to the exception of
tp_connection_dup_contact_list). and probably GList is cheap to deepcopy wi=
th
slice allocator=E2=80=A6

I still have that crazy idea that stuff like "return
g_object_unref_in_idle(obj)" would be useful to let a chance to caller to t=
ake
its ref while not introducing a leak if he does not care about return value.

And to finish, if we go with GList, please make it (transfer full/none), but
(transfer container) is just confusing IMO.

--=20
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=3Demail
------- You are receiving this mail because: -------
You are the QA Contact for the bug.
You are the assignee for the bug.=