We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I had a data that looked like this:
data: ast::Data<darling::util::Ignored, MyField>,
and I implemented UsesTypeParams and UsesLifetimes for MyField, so I could use data.uses_type_params_cloned and everything was great.
UsesTypeParams
UsesLifetimes
data.uses_type_params_cloned
Then I needed access to the original syn::Field, so I found WithOriginal, and changed my data to this:
syn::Field
data: ast::Data<darling::util::Ignored, WithOriginal<MyField, syn::Field>>,
but this broke data.uses_type_params_cloned (and uses_lifetimes_cloned) because WithOriginal does not implement these two traits.
Wouldn't it make sense for WithOriginal to forward these traits to the parsed type?
The text was updated successfully, but these errors were encountered:
Yes, that sounds reasonable to me.
Sorry, something went wrong.
No branches or pull requests
I had a data that looked like this:
and I implemented
UsesTypeParams
andUsesLifetimes
for MyField, so I could usedata.uses_type_params_cloned
and everything was great.Then I needed access to the original
syn::Field
, so I found WithOriginal, and changed my data to this:but this broke
data.uses_type_params_cloned
(and uses_lifetimes_cloned) because WithOriginal does not implement these two traits.Wouldn't it make sense for WithOriginal to forward these traits to the parsed type?
The text was updated successfully, but these errors were encountered: