A lot of stuff private to the EDK does not need to be private, and will be useful to consumers of the new Mojo invitation API once landed.
This is stuff like PlatformChannelPair, ScopedPlatformHandle, and various utility functions.
We should introduce mojo/public/cpp/platform_support for this stuff, and then we can also build a C++ invitation API in mojo/public/cpp/system, based on platform_support and the C invitation API.
All direct EDK calls apart from basic initialization can then be migrated over to public API calls.
Comment 1 by roc...@chromium.org
, May 18 2018