Simplify illustrative example
This commit is contained in:
parent
202d92d237
commit
486528416d
|
@ -81,13 +81,11 @@ serializing in some other implementation-defined order.
|
|||
ordering is required.
|
||||
|
||||
[^not-sorted-semantically]: It's important to note that the sort
|
||||
ordering for writing out set elements and dictionary key/value
|
||||
pairs is *not* the same as the sort ordering implied by the
|
||||
semantic ordering of those elements or keys. For example, the
|
||||
`Repr` of a negative number very far from zero will start with
|
||||
byte that is *greater* than the byte which starts the `Repr` of
|
||||
zero, making it sort lexicographically later by `Repr`, despite
|
||||
being semantically *less than* zero.
|
||||
ordering for writing out set elements and dictionary key/value pairs
|
||||
is *not* the same as the sort ordering implied by the semantic
|
||||
ordering of those elements or keys. For example, the `Repr` of a
|
||||
negative number sorts lexicographically *after* the `Repr` of zero,
|
||||
despite being semantically *less than* zero.
|
||||
|
||||
**Rationale**. This is for ease-of-implementation reasons: not all
|
||||
languages can easily represent sorted sets or sorted dictionaries,
|
||||
|
|
Loading…
Reference in New Issue