I remember we went through quite some trouble when trying to build C core so that it is compatible with wide range of libc versions. I expect things to become even worse when libc++ comes into play. My guesstimate is that introducing C++ into C core would cost 2 weeks of work & testing per wrapped language to make sure everything works the way it should (especially around the distribution packages & platform compatibility etc.) I'm not 100% sure if we could make things work for all languages without harming usability (but I can be convinced - it would be worth to experiment with one wrapped lang. before we decide to go ahead).
On Saturday, April 1, 2017 at 4:39:49 PM UTC+2, Craig Tiller wrote: > > https://github.com/grpc/grpc/pull/10426 and > https://github.com/grpc/grpc/pull/10427 start to show what this might > look like. > > On Sat, Apr 1, 2017 at 7:33 AM Craig Tiller <[email protected] > <javascript:>> wrote: > >> I've created a proposal to allow C++ to be used in gRPC Core here: >> https://github.com/grpc/proposal/pull/21. >> >> I'm especially interested in hearing from folks in environments where >> this won't work well. >> > -- 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/2e080e70-29b0-4c60-9379-3459ffd3fa4f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
