Codey Oxley
Codey Oxley
There seems to be an unfinished and undocumented feature that gets pulled in by default, conflicting with `protoc-gen-go-grpc`. Should this be excluded from the default feature list? - https://github.com/planetscale/vtprotobuf/tree/main/features/grpc
Just wanted to pop in after reading [your HTTP/2 blog post](https://morsmachine.dk/http2-causalprof) and say this is wicked cool. ❤️ I'd never heard of causal profiling before, and seeing it in practice...
@kylechui Unfortunately the default "target" for `vim.lsp.buf.rename()` is ``, which means this can't work in the context of surround. :\
@arvindbr8: Any idea when we can get this patched in? :)
@ohaibbq: Oh dang, I completely missed that in the documentation. Thank you very much. I guess my real issue is with `internalError` then.
I was looking for the same!
@milkpirate So because `fig` uses `mitchellh/mapstructure` under the hood, you can include `,squash` in your configured tag for the field. ```go type Base struct { Env string `fig:"env"` } type...
@jzelinskie: I don't personally have a strong opinion, but the example approach would fit given that's what is done for supporting both vtproto and standard in a single codec.
Also, while someone can generate only `SizeVT()`, they cannot use `MarshalVT()` without it. The generated marshaling code assumes size exists.
@vmg Something that may be neat is finally being able to use pooled vtproto objects for unary client and servers. It’d be a bit wonky — it would rely on...