3 Commits

Author	SHA1	Message	Date
Damien Neil	c7f2beeef0	internal/impl: assume legacy Marshal method supports deterministic ... The v1 implementation calls Marshal methods when deterministic serialization is requested, even though it has no way to verify that the method supports determinism. Preserve this behavior. Change-Id: I383f2ec4bd4d5b996d96d604e92dfa43cb6f1bdc Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/205719 Reviewed-by: Joe Tsai <thebrokentoaster@gmail.com>	2019-11-07 00:44:29 +00:00
Damien Neil	47d5893acf	internal/impl: support non-struct-pointer legacy message types ... Support, to some limited degree, types which implement protoV1.Message but which are not struct pointers. Our ability to work with these types is largely limited to calling Marshal or Unmarshal methods, when present. Change-Id: Ie1b851d9e753e2b2cb189b17ffeefebe2d8b3a8f Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/198237 Reviewed-by: Joe Tsai <thebrokentoaster@gmail.com>	2019-10-04 16:13:03 +00:00
Damien Neil	37ef691e6b	internal/impl: call Marshal/Unmarshal methods on legacy types ... Call the Marshal or Unmarshal method on legacy messages implementing protoV1.Marshaler or protoV2.Unmarshaler. We do this in the impl package by creating an appropriate function in the protoiface.Methods struct for legacy messages. In proto.MarshalAppend, return the bytes provided by the fast-path marshal function even when the returned error is non-nil. Fixes golang/protobuf#955 Change-Id: I36924af9ff959a946c43f2295ef3202216e81b32 Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/197357 Reviewed-by: Joe Tsai <joetsai@google.com>	2019-09-26 20:54:39 +00:00