Joe Tsai 00a323deed internal/impl: use XXX_unrecognized exclusively for unknown fields ...

The protobuf data model makes no distinction between unknown fields
that are within the extension field ranges or not. Now that we eagerly
unmarshal extensions, there is even less need for storing unknown
fields in the extension map. Instead, use the XXX_unrecognized field
exclusively for this purpose.

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

2019-05-09 01:26:50 +00:00

..

export.go

encoding/textpb: add AllowPartial option to MarshalOptions and UnmarshalOptions

2019-03-27 17:23:26 +00:00

legacy_export_test.go

all: move v1 types over to the v2 repository

2019-03-22 20:01:07 +00:00

legacy_export.go

runtime/protoimpl: remove ExtensionFieldsV1

2019-04-16 23:53:07 +00:00

legacy_extension.go

internal/impl: use XXX_unrecognized exclusively for unknown fields

2019-05-09 01:26:50 +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/impl: use XXX_unrecognized exclusively for unknown fields

2019-05-09 01:26:50 +00:00

legacy_unknown.go

internal/impl: use XXX_unrecognized exclusively for unknown fields

2019-05-09 01:26:50 +00:00

message_field.go

internal/{fileinit,impl}: minimal weak field support

2019-05-08 17:24:54 +00:00

message_test.go

internal/impl: fix Has behavior for floats

2019-04-22 20:01:26 +00:00

message.go

internal/{fileinit,impl}: minimal weak field support

2019-05-08 17:24:54 +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