Add test vector for that uses traits and associated types in a contract - #1598
Merged
Conversation
leighmcculloch
marked this pull request as ready for review
October 17, 2025 06:36
leighmcculloch
enabled auto-merge
October 20, 2025 03:32
dmkozh
approved these changes
Oct 20, 2025
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
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.
What
Add test vector for trait associated types in contracts, demonstrating the pattern where a trait uses associated types to delegate to default implementations.
Why
The OpenZeppelin contract library uses this pattern, and having test vector that uses the pattern provides some visibility to how the generated code expands alongside associated types.
For #1544