mirror/protobuf-go
1
0
Fork 0
mirror of https://github.com/protocolbuffers/protobuf-go.git synced 2025-01-01 11:58:21 +00:00
Code Issues Packages Projects Releases Wiki Activity
Go support for Google's protocol buffers
641 Commits 1 Branch 27 Tags 20 MiB
Go 99.8%
Shell 0.2%
96a44732e0
Go to file
Joe Tsai 96a44732e0 proto: distinguish between invalid and empty messages in Equal 
The v1 proto.Equal function treats (*Message)(nil) and new(Message)
as being different, while v2 proto.Equal treated them as equal since
a typed nil pointer is functionally an empty message since the
protobuf data model has no concept of presence as a first-class
property of messages.

Unfortunately, a significant amount of code depends on this distinction
that it would be difficult to migrate users from v1 to v2 unless we
preserved similar semantics in the v2 proto.Equal.

Also, double down on these semantics for protocmp.Transform.

Fixes #965

Change-Id: I21e78ba6251401a0ac0ccf495188093973cd7f3f
Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/213238
Reviewed-by: Damien Neil <dneil@google.com>
2020-01-06 19:37:38 +00:00
benchmarks benchmarks: move download_benchdata.bash into benchmarks/ dir 2019-07-09 22:36:27 +00:00
cmd cmd/protoc-gen-go: remove json ignore tags 2019-12-10 23:22:16 +00:00
compiler/protogen reflect/protoregistry: add (*Types).Register{Message,Enum,Extension} 2019-10-31 16:23:42 +00:00
encoding encoding/prototext: fix crash in map parsing 2019-12-25 06:02:31 +00:00
internal internal/impl: return nil for nil enum or message 2020-01-06 19:10:59 +00:00
proto proto: distinguish between invalid and empty messages in Equal 2020-01-06 19:37:38 +00:00
reflect internal/filedesc: use jsonName.Init method over JSONName constructor 2020-01-06 18:42:14 +00:00
runtime proto: reset message by default in Unmarshal 2019-09-17 21:13:42 +00:00
testing proto: distinguish between invalid and empty messages in Equal 2020-01-06 19:37:38 +00:00
types all: fix reflection behavior for empty lists and maps 2019-11-26 22:58:51 +00:00
.gitignore internal/fuzz: add basic fuzzing target for Marshal/Unmarshal 2019-10-11 16:00:11 +00:00
.travis.yml .travis.yml: configure for OSX 2019-03-13 18:04:08 +00:00
AUTHORS AUTHORS, CONTRIBUTORS, LICENSE, PATENTS: initial commit 2018-08-07 22:39:48 +00:00
CONTRIBUTING.md CONTRIBUTING.md: add pre-push hook instructions 2018-08-07 23:58:41 +00:00
CONTRIBUTORS AUTHORS, CONTRIBUTORS, LICENSE, PATENTS: initial commit 2018-08-07 22:39:48 +00:00
go.mod reflect/protoregistry: remove deprecated APIs 2019-11-08 01:03:52 +00:00
go.sum reflect/protoregistry: remove deprecated APIs 2019-11-08 01:03:52 +00:00
integration_test.go all: update to go1.13 release 2019-09-06 18:27:08 +00:00
LICENSE AUTHORS, CONTRIBUTORS, LICENSE, PATENTS: initial commit 2018-08-07 22:39:48 +00:00
PATENTS AUTHORS, CONTRIBUTORS, LICENSE, PATENTS: initial commit 2018-08-07 22:39:48 +00:00
README.md CONTRIBUTING.md: initial commit 2018-08-01 20:39:06 +00:00
regenerate.bash internal/cmd/generate-protos: generate test for testdata 2019-03-11 19:40:53 +00:00
release.bash release.bash: add support for building release binaries 2019-08-21 01:15:26 +00:00
test.bash test.bash: add -failfast flag 2019-08-05 21:48:09 +00:00

README.md

Next Generation Go Protocol Buffers

WARNING: This repository is in active development. There are no guarantees about API stability. Breaking changes will occur until a stable release is made and announced.

This repository is for the development of the next major Go implementation of protocol buffers. This library makes breaking API changes relative to the existing Go protobuf library. Of particular note, this API aims to make protobuf reflection a first-class feature of the API and implements the protobuf ecosystem in terms of reflection.

Design Documents

List of relevant design documents:

Contributing

We appreciate community contributions. See CONTRIBUTING.md.

Reporting Issues

Issues regarding the new API can be filed at github.com/golang/protobuf. Please use a APIv2: prefix in the title to make it clear that the issue is regarding the new API work.