Hi there, I'd very much like to discuss this issue. Switching to explicit initialization increases friction for users, but keeping it the existing way just increases friction for the library writers (unless the code ends up being so failure-prone that it affects users through a loss of stability). Has there been a user feature request for explicit initialization?
On Tuesday, December 12, 2017 at 9:40:21 AM UTC-8, Yang Gao wrote: > > Hi, > > I have created a gRFC in https://github.com/grpc/proposal/pull/48 which > will add a new C++ class to make gRPC C++ library lifetime explicit. > If you have comments and suggestions, please use this thread to discuss. > Thanks. > -- 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 grpc-io+unsubscr...@googlegroups.com. To post to this group, send email to grpc-io@googlegroups.com. 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/79d883f9-cbc3-4281-9c16-3f5b7edaff3e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
