Joshua Humphries

I won't be able to approve/merge any changes as I'm no longer with FullStory. However, I can provide some input on the above described solution: 1. I wouldn't put it...

FWIW, this can also be accomplished using _proto_ reflection instead of Go reflection. This approach is a bit more general since it handles cases where the protoc plugin has to...

Another thing we talked about, though maybe it would be in a post-v1 version, is configuring a minimum number of connections. This is useful for cases where address resolution returns...

Final related tidbit: it would be ideal if we could override the "maximum concurrent streams" in the server's settings frame -- like to tell the client to only allow a...

FWIW, that pending PR was #354. And it has now been merged and released in v1.15. There is still no direct interop support between `dynamic.ExtensionRegistry` and the newer runtime API...

@btiernay, you may have already seen it, but [v1.15](https://github.com/jhump/protoreflect/releases/tag/v1.15.0) introduced some major changes that should make interop between this module and the `reflect/protoreflect` stuff in `google.golang.org/protobuf` drastically better (almost all...

@LSTPro, that's really a grpc-go question, not specific to this repo. https://github.com/grpc/grpc-go/blob/master/Documentation/grpc-metadata.md#receiving-metadata

@WillAbides, any future changes to the parser should be done in https://github.com/bufbuild/protocompile. There are a large number of test cases in that repo that are compared against `protoc` automatically, by...

I've finally confirmed with `apidiff` that this should be a compatible change -- no incompatible changes made to exported APIs. The only changes are below (all additions, which are compatible...

Closing as won't fix. Instead, use https://github.com/bufbuild/protocompile. When you get back a file descriptor from the `protocompile.Compiler`, if it will type assert to `linker.Result`, then you can call that type's...