|
|
|
|
|
by madgar
3612 days ago
|
|
> designing a protocol It's not a full protocol. It's a data type for a serialization library. You can write your own data types and they serialize just as well as the built-in types. > that breaks interoperability Wait, what was "broken" here? What was working before that isn't with this new release? What does this inclusion of a utility data type in a serialization library break that previously was intact? |
|