Open mkschreder opened 4 months ago
No, the code generator does not yet use the unordered maps API, but this is planned to be implemented soon-ish.
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.
It seems that current code generator is still outputting code that expects map keys in the exact order that they are defined in cddl.
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?