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
We generally don’t want to add more types to be binary serializable in the framework, due to complexities and the fragility that it causes across version boundaries (remember that binary serialization has to be backward- and forward compatible). That being said, for ValueTuple we can likely convince ourselves that the serialization behavior is fixed and mostly a function of the types you instantiate the tuple with. It seems a resonable assumption to say that ValueTuple<T1, ..., TN> to be serializable if T1-TN are serializable.
Not being binary serializable also makes it harder (and more fragile) for existing code to switch from Tuple to ValueTuple.
The text was updated successfully, but these errors were encountered:
We generally don’t want to add more types to be binary serializable in the framework, due to complexities and the fragility that it causes across version boundaries (remember that binary serialization has to be backward- and forward compatible). That being said, for
ValueTuple
we can likely convince ourselves that the serialization behavior is fixed and mostly a function of the types you instantiate the tuple with. It seems a resonable assumption to say thatValueTuple<T1, ..., TN>
to be serializable ifT1
-TN
are serializable.Not being binary serializable also makes it harder (and more fragile) for existing code to switch from
Tuple
toValueTuple
.The text was updated successfully, but these errors were encountered: