tree 170c757c43a8bde6b5aab8f94942be5e4a0ca66e
parent fd04762ad2e48358a73a5b577e965b050c359e13
author Toshi Kikuchi <toshik@google.com> 1565214918 -0700
committer CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> 1566502066 +0000

[fidl][go] Fix an empty response from a protocol method

Currently, both these two protocol method definitions generate
Dispatch() that returns nil as a response:

1. Foo()        // no response.
2. Foo() -> ()  // the response is empty.

And the current Go bindings always thinks the nil response means
(1). Calling the method defined as (2) would get stuck because
there is no response coming back.

To fix (2), we replace Dispatch() with DispatchImpl() that returns
an extra boolean flag that tells if a response is required or
not. If the response is nil but the flag is true, Go bindings
can tell it is (2).

Bug: 8098
Change-Id: I5d814d164dc43c0e0c4b8a025b8925d455a38480