How does decoding unordered maps work?

[mkschreder]

It seems that current code generator is still outputting code that expects map keys in the exact order that they are defined in cddl.

Type = {
   key_a: int,
   key_b: int
}

The code generated from this will be a long if statement where the fields are in exact order with && between. So decoding in any order does not work.

Is there a workaround for this?

[oyvindronningstad]

No, the code generator does not yet use the unordered maps API, but this is planned to be implemented soon-ish.

[mkschreder]

I think it's really important because the following passage of the specification does not hold true for the current decoder:

In the current implementation the map behaves like a list where all fields must come in exact order.

[sam-golioth]

@oyvindronningstad Any update on a timeline for this? The spec clearly states that maps must be processed unordered, this makes the ZCBOR generated code incompatible with any other serialization library that is spec compliant, which makes CDDL generation essentially unusable for communication with any other systems that aren't using ZCBOR.