Code review comment for lp:~vanvugt/mir/wait-result

On Thu, Mar 19, 2015 at 1:37 PM, Daniel van Vugt
<email address hidden> wrote:
> Ah, what you might be talking about is multiple threads doing the
> same thing. Indeed in that case calling _get will be racy. There's no
> guarantee that w represents the request for Y in that case.

Not even multiple threads doing the same thing; the server can change
the surface state without the client requesting it (obvious example is
drag-title-bar-to-unmaximise), and that event can be processed before
the thread executing mir_wait_for continues execution.

Surface states are event driven; attempts to make them appear otherwise
make the client API harder to use.