[roll] Roll fuchsia [fidl][cpp] Move event dispatch out of ClientBase

This CL pulls the DispatchEvent virtual method into its own interface.
This allows us to specify event dispatch logic without inheriting from
ClientBase (as is to be done in the unified bindings).

At this point, ClientBase has no virtual methods anymore, so it's
possible to stop inheriting from ClientBase, instead using composition.
That's reserved to a future CL to keep patches small.

The astute reader may also realize that WireEventDispatcher (used in
async clients) is looking almost identical to
WireSyncEventHandler::HandleOneEvent. With some effort we could merge
the two. That's reserved to a future CL to keep patches small.

Original-Bug: 82085

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/619563
Original-Revision: a7ad3ddb984e9abb3d7b94ae4a5375f7007ff4f6
GitOrigin-RevId: 996479993507cf90870cc0d5581e36c293b62361
Change-Id: I0e52bf894573d4d82374395c85381931fa2fafb7
1 file changed
tree: 9cf9420fc68c76ae1ed7263ad1e76f463e9a2b1b
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.