Handle tuple variants in complex enums #14
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
Author
|
Kicked CI which was failing due to the lack of lightningdevkit/ldk-c-bindings#9 - should work now. |
arik-so
approved these changes
Mar 30, 2021
TheBlueMatt
force-pushed
the
2021-03-fix-enums
branch
from
ac841ca to
963dba5
Compare
Collaborator
Author
|
Only change was temporary variables as Arik suggested. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes tuple variants in enums, also exposing the new Option enums. It does drop the manual enum variant constructors in favor of the auto-generated ones from the Rust constructor functions.