-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
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
Think hard about how to handle CHOICE #19
Comments
Fundamentally the only possible API here is:
Implementation is straightforward pending figuring out implicit/explicit tagging |
I think you can basically treat a choice as a sequence of optionals (possibyl with explicit/implicit tags) where at least one must have a value. |
Ok, better plan: enum Choice2<T1: Asn1Element, T2: Asn1Element> {
Element1(T1::Output),
Element2(T2::Output),
} we can generate 2-5 of these or so. |
This worked out easily enough, solved in #54 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: