In #57 and #62 we moved from treating bool and enums as primitives with bytes to semantic values that can only be checked with patterns/ifs. This is good in terms of the harness not making up garbage values for "expect" and clean clear output, but it would be nice if we got the bytes of them too since often an ABI corruption will write forbidden values that don't make sense.
Right now this is tricky to do because the harness believes each "value" (field) can only have one payload (bytes). This would result in enums and bools having two payloads: the semantic tag, and the raw bytes.
In #57 and #62 we moved from treating
booland enums as primitives with bytes to semantic values that can only be checked with patterns/ifs. This is good in terms of the harness not making up garbage values for "expect" and clean clear output, but it would be nice if we got the bytes of them too since often an ABI corruption will write forbidden values that don't make sense.Right now this is tricky to do because the harness believes each "value" (field) can only have one payload (bytes). This would result in enums and bools having two payloads: the semantic tag, and the raw bytes.