Hein Meling

After a more thorough examination, I have concluded that interceptors are not appropriate for our use case. What we should have is something more akin to a client-side proxy, that...

Here are some more thoughts on the issue of interceptors. gRPC does not support other `Interceptor/Invoker` types than these: ```go type StreamClientInterceptor type StreamServerInterceptor type UnaryClientInterceptor type UnaryInvoker type UnaryServerInterceptor...

@qianlnk Looked at your `retag` plugin as one of several alternatives. I don't really like the idea of cloning it into my `golang/protobuf` folder, especially since `This branch is 8...

@dsnet See [tags.proto](https://github.com/gogo/protobuf/blob/master/test/tags/tags.proto) which was referred to by @awalterschulze as an example of using the protobuf options approach. It could perhaps look something like this: ```proto message Enrollment { uint64...

@dsnet Regarding your point about opaque types. I think there are two main use cases that have come up in this issue. 1. Boilerplate avoidance for database/storage backends. 2. Validation...

A global option may work for your use case with `bson`, but many other use cases require per field options.

Why is it crazy to define `index` fields using standard protobuf options syntax? I didn’t design the option syntax for protobuf, but I learn to adapt. Just because something is...

You are right of course. I guess adding such a feature now would at least help people in the future. Another solution could be to add a flag `--overwrite_only_newer` (tentatively...

Thanks for the input and proposed combined generator; much appreciated. I had been looking at the Map and FlatMap before, but found it a bit difficult to understand without a...

Thanks! I actually just discovered the same myself after you pointed out that I was returning a generator, which I thought was awkward... So that solved it!! Thanks for helping...