Damien Neil 8c86fc5e7d all: remove non-fatal UTF-8 validation errors (and non-fatal in general) ... Immediately abort (un)marshal operations when encountering invalid UTF-8 data in proto3 strings. No other proto implementation supports non-UTF-8 data in proto3 strings (and many reject it in proto2 strings as well). Producing invalid output is an interoperability threat (other implementations won't be able to read it). The case where existing string data is found to contain non-UTF8 data is better handled by changing the field to the `bytes` type, which (aside from UTF-8 validation) is wire-compatible with `string`. Remove the errors.NonFatal type, since there are no remaining cases where it is needed. "Non-fatal" errors which produce results and a non-nil error are problematic because they compose poorly; the better approach is to take an option like AllowPartial indicating which conditions to check for. Change-Id: I9d189ec6ffda7b5d96d094aa1b290af2e3f23736 Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/183098 Reviewed-by: Joe Tsai <thebrokentoaster@gmail.com>		2019-06-20 20:55:13 +00:00
..
protojson	all: remove non-fatal UTF-8 validation errors (and non-fatal in general)	2019-06-20 20:55:13 +00:00
prototext	all: remove non-fatal UTF-8 validation errors (and non-fatal in general)	2019-06-20 20:55:13 +00:00
testprotos	cmd/protoc-gen-go: un-deprecate enum maps	2019-06-20 19:36:37 +00:00
bench_test.go	reflect/protoreflect: add alternative message reflection API	2019-06-17 17:33:24 +00:00