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
The documentation for msgp -unexported says that it will process unexported types (like type myint int), but it has the unexpected additional behavior of encoding and decoding unexported fields (like type Foo struct { hidden int }). This can be a significant change in behavior in scenarios where the developer was expecting unexported fields to be hidden at encoding time and to be preserved at decoding time.
It would be great to reconcile the documentation with behavior of -unexported, ideally by not encoding/decoding unexported struct fields.
The text was updated successfully, but these errors were encountered:
The documentation for
msgp -unexported
says that it will process unexported types (liketype myint int
), but it has the unexpected additional behavior of encoding and decoding unexported fields (liketype Foo struct { hidden int }
). This can be a significant change in behavior in scenarios where the developer was expecting unexported fields to be hidden at encoding time and to be preserved at decoding time.It would be great to reconcile the documentation with behavior of
-unexported
, ideally by not encoding/decoding unexported struct fields.The text was updated successfully, but these errors were encountered: