> Why does mir_surface_apply_spec return a MirWaitHandle? I don't particularly
> mind it doing so, but as (extensively!) discussed, there's nothing useful a
> client can do with it.
I agree it is useless. But it is consistent with the other APIs we discussed. Is it better to be inconsistent and return void now? Or to plan on removing the wait handle in all similar APIs when we next break ABI compatibility?
*Needs Discussion*
> Why does mir_surface_ apply_spec return a MirWaitHandle? I don't particularly
> mind it doing so, but as (extensively!) discussed, there's nothing useful a
> client can do with it.
I agree it is useless. But it is consistent with the other APIs we discussed. Is it better to be inconsistent and return void now? Or to plan on removing the wait handle in all similar APIs when we next break ABI compatibility?