We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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?
The text was updated successfully, but these errors were encountered:
No, the code generator does not yet use the unordered maps API, but this is planned to be implemented soon-ish.
Sorry, something went wrong.
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.
Successfully merging a pull request may close this issue.
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?
The text was updated successfully, but these errors were encountered: