gspawn: Mark child setup in g_spawn_sync() as call scope

While it's only called one time, this is something that can only happen
during the function call, so it's more correct to mark it as call scope,
so that bindings don't have to wait for the callback invocation to
cleanup the data.
This commit is contained in:
Marco Trevisan (Treviño) 2023-08-10 23:28:28 +02:00
parent ff23b24254
commit 694eb3aa02

View File

@ -333,7 +333,7 @@ read_data (GString *str,
* @envp: (array zero-terminated=1) (element-type filename) (nullable):
* child's environment, or %NULL to inherit parent's
* @flags: flags from #GSpawnFlags
* @child_setup: (scope async) (closure user_data) (nullable): function to run
* @child_setup: (scope call) (closure user_data) (nullable): function to run
* in the child just before `exec()`
* @user_data: user data for @child_setup
* @standard_output: (out) (array zero-terminated=1) (element-type guint8) (optional): return location for child output, or %NULL