You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bar will return the same value for MethodOptions.uninterpreted_option in both protoc and goprotoc, but Baz will have an empty non-nil array in goprotoc, and a nil array in protoc.
This is whatever the opposite of important is, but is getting in the way of automated protoc vs goprotoc testing with proto.Equal unfortunately.
I really thought we dealt with {} vs ;, maybe this is a "regression" ie 3.9.0 is doing something different (the above was done with protoc 3.9.0). EDIT: Also done with protoc 3.7.1, happens with 3.7.1 as well.
The text was updated successfully, but these errors were encountered:
I could have sworn we dealt with this, but I can't find the issue.
Example:
Bar
will return the same value forMethodOptions.uninterpreted_option
in bothprotoc
andgoprotoc
, butBaz
will have an empty non-nil array ingoprotoc
, and a nil array inprotoc
.This is whatever the opposite of important is, but is getting in the way of automated
protoc
vsgoprotoc
testing withproto.Equal
unfortunately.I really thought we dealt with
{}
vs;
, maybe this is a "regression" ie 3.9.0 is doing something different (the above was done withprotoc
3.9.0). EDIT: Also done withprotoc
3.7.1, happens with 3.7.1 as well.The text was updated successfully, but these errors were encountered: