mirror of
https://github.com/protocolbuffers/protobuf-go.git
synced 2025-01-04 02:38:50 +00:00
21e33cc910
There are inconsistencies between implementations on what happens when a single program contains generated code for multiple files with the same source path. At least one canonical implementation (C++) will fail at link time. Others print warnings. Some silently resolve the registry conflict in favor of one file or the other. The protobuf maintainers agree, however, that the desired behavior is for this condition to be an error. Updates golang/protobuf#1122 Change-Id: I716708f16ef90210bdfceb0888691e47783df172 Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/322729 Trust: Damien Neil <dneil@google.com> Reviewed-by: Joe Tsai <thebrokentoaster@gmail.com> |
||
|---|---|---|
| .. | ||
| protodesc | ||
| protopath | ||
| protorange | ||
| protoreflect | ||
| protoregistry | ||