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 non-human readable serialization of SocketAddrV6 (and by extension SocketAddr) encodes only IP address and port information, omitting flow info and scope:
I have already dug around the commit logs to see if there was a reason, but as far as I can tell it was just an oversight.
The fix is obvious and trivial, and I'm happy to do the PR. But before doing so I wanted to find out whether there is some existing mechanism to use when introducing backwards incompatible changes to serialized representations like this?
The text was updated successfully, but these errors were encountered:
The non-human readable serialization of
SocketAddrV6
(and by extensionSocketAddr
) encodes only IP address and port information, omitting flow info and scope:serde/serde/src/ser/impls.rs
Lines 857 to 874 in ddc1ee5
I have already dug around the commit logs to see if there was a reason, but as far as I can tell it was just an oversight.
The fix is obvious and trivial, and I'm happy to do the PR. But before doing so I wanted to find out whether there is some existing mechanism to use when introducing backwards incompatible changes to serialized representations like this?
The text was updated successfully, but these errors were encountered: