-
Notifications
You must be signed in to change notification settings - Fork 28
Add a new TypeDef variant to handle PhantomData #48
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
Conversation
ascjones
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just need to fix the identity of PhantomData<T>, some tests may fail
ascjones
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Robbepop
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All in all code looks good.
The only thing I am missing is an in-depth comment explaining the design rationals behind this PR so that we won't forget why we chose this design instead of others we previously talked about. I always love finding such comments when I forgot about certain rationals after months of not looking at the issue.
Make From impl consistent with other types of types
|
I'd love to have the example of reconstructing rust types given the scale info metadata as motivation for having PhantomData deginitions. |
See #31 (comment) for the background.
Supersedes #31
Closes #7
Note that we do not yet have support for
#[codec(skip)](implemented in PR #44) so when that lands we'll want to amend the tests here (or there, if this lands first).