Remove gogo protobuf
Yes, I am moving go-libp2p-kad-dht away from gogo, and there is a dependency on go-libp2p-record. The plan is to make a new release of go-libp2p-record so that consumers can move away from gogo when they are ready.
@vyzo
you need to consider downstream consumers who are probably still using gogo with the generated code, which are likely to break.
Why would downstream consumers be impacted? They just use the generated file, no?
there might be some api changes.
The api changes are just that Marshal/Unmarshal are not methods on the generated structs, but instead functions that use reflect in the proto package. It's also missing the MarshalTo(SizedBuffer) method.
Should be a relatively straightforward change when upgrading.