This repository has been archived by the owner on Oct 19, 2024. It is now read-only.
feat: add support for multiple contract definitions in abigen macro #498
Conversation
This file contains 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
gakonst
approved these changes
Oct 11, 2021
| impl Parse for Contracts { | ||
| fn parse(input: ParseStream) -> ParseResult<Self> { | ||
| let inner = input | ||
| .parse_terminated::<_, Token![;]>(ContractArgs::spanned_parse)? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Motivation
This allows to use same ABIEncoderV2 structs for multiple structs.
Solution
Make abigen! parse 1+ Contract definition and then adjust for type conflicts by extracting them into a separate
__shared_typesmodule from where the contract mods then import.contract definitions within abigen are now separated by
;, this is a non-breaking change so that abigen!(single contract) still works the same.PR Checklist