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

The value of this branch is more clear in the surface morphing prototype:
https://code.launchpad.net/~vanvugt/mir/rename-api/+merge/252864

It's not "pointless". It is /probably/ required that the client be told if their multi-attribute modification has happened or not. In the latter "not" case there is no event to wait for. So you need this wait-for-result, or something similar like wait-for-error-code-or-success.

In the mean time, it hurts nobody to not land anything in this area. Just that we'll soon have a situation where some features of the client API can't return errors to the client. Which might turn out to be acceptable...