Joe Tsai 22b1ebd068 internal/impl: split messageWrapper into different types ...

The previous implementation of messageWrapper implemented both
proto.Message and protoreflect.Message. This made it possible for users
to accidentally rely on this fact when it was actually an internal
implementation detail.

To avoid this, we split the wrapper type into two, ensuring that each
only implements one or the other. Doing so also revealed bugs in our
own code where we accidentally relied on this fact.

Change-Id: I0ff521b5c806b7dcb0b86942bd97e8319d8e8657
Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/166938
Reviewed-by: Damien Neil <dneil@google.com>

2019-03-11 21:23:31 +00:00

..

export.go

reflect/protoreflect: drop the ProtoEnum type

2019-01-09 00:40:35 +00:00

legacy_extension.go

internal/fileinit: generate reflect data structures from raw descriptors

2019-01-30 01:33:46 +00:00

legacy_hook.go

internal/legacy: extract legacy support out from the impl package

2018-11-30 23:16:16 +00:00

legacy_test.go

internal/fileinit: generate reflect data structures from raw descriptors

2019-01-30 01:33:46 +00:00

legacy_unknown.go

internal/fileinit: generate reflect data structures from raw descriptors

2019-01-30 01:33:46 +00:00

message_field.go

reflect: switch MessageType.New to return Message

2019-01-09 20:29:29 +00:00

message_test.go

internal/impl: drop MessageType.(Unk|K)nownFieldsOf

2019-01-30 01:34:45 +00:00

message.go

internal/impl: split messageWrapper into different types

2019-03-11 21:23:31 +00:00

pointer_reflect.go

all: add appengine build tag

2018-12-19 00:36:57 +00:00

pointer_unsafe.go

all: add appengine build tag

2018-12-19 00:36:57 +00:00