> This is a proposal to curate the contents of the include/grpc/support
> directory, which is the public surface of the GPR API, as many of the
> entries in that API are not actually publicly needed or used. The result
> will be a smaller installation and fewer API surface points.
Seems reasonable for my use of gRPC, and the uses I've observed.
Here's a conservative list of the gpr functions that my codebase uses.
* gpr_set_allocation_functions & data structures
* If this function stays, the getter should probably stay too.
* gpr_set_log_function & data structures
* We're not using the gpr_log* functions directly.
* The gpr_time* functions, as these types are part of the C++ Alarm API
* We're not using gpr_sleep_until
--
Christopher Warrington
Microsoft Corp.
--
You received this message because you are subscribed to the Google Groups
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit
https://groups.google.com/d/msgid/grpc-io/485b4a53-af51-4d0f-ae26-2b6317a2ef3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
