The single-statement form answers with a bare ResultSet; the batch form
answers with {"results": [ … ]}. Both are accepted here because the adapter
uses both.
It was, and the attribute defeated this module’s stated reason for existing.
Untagged deserialisation tries each variant and, when none fits, reports
data did not match any variant of untagged enum ResponseBody — with no
field, no offset and no indication of which shape was closer. A drift in
ResultSet would surface as that sentence rather than as
missing field 'rows', which is exactly the “a None three layers down”
failure the module docs above say the typed shapes exist to prevent.
parse branches on the presence of results first and then
deserialises the chosen shape, so a malformed body reports the field it
tripped on.
Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.