I've gotten a question about whether this implies that gRPC will throw exceptions. The idea that we will catch exceptions is separate from the idea of throwing exceptions, and we can happily do the former without doing the latter. The googletest library is a great example here; it catches exceptions (and marks tests failed that have exceptions) but does not itself throw exceptions. It also builds just fine in platforms that don't allow exceptions. This gRFC says that gRPC should behave the same way.
On Tuesday, December 19, 2017 at 3:45:01 PM UTC-8, Vijay Pai wrote: > > Hi all, > > I have posted a new proposal at https://github.com/grpc/proposal/pull/51 > to help improve server robustness in the presence of method handlers that > trigger C++ exceptions. Please feel free to discuss in this thread. > > Regards, > > vjpai > > -- 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/642f6900-5100-4107-8235-ce278736aa81%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
