3 ms·
This isn't really an issue of spec because these systems recognize a completely different protocol 'OrderedJSON' which interprets {} as an ordered list of key-v
by Spivak 7y ago
This isn't really an issue of spec because these systems recognize a completely different protocol 'OrderedJSON' which interprets {} as an ordered list of key-value pairs instead of a set.
The mistake is assuming that two syntactically compatible protocols were actually the same protocol. uint =! int.
- coldtea 7y agoOnly there's no such protocol. It's some adhoc implementation within a single system (or a single IBM ecosystem).