Even though it's not strictly necessary here, it's a good style to follow. It reduces the chances of re-using the same GError without ensuring that it is empty, and emphasizes that g_task_return_error assumes ownership of the GError.
Even though it's not strictly necessary here, it's a good style to follow. It reduces the chances of re-using the same GError without ensuring that it is empty, and emphasizes that g_task_return_error assumes ownership of the GError.