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
The title says it all - if we do:
#[account] struct MyAccount { data: GStruct<u32>, } #[derive(AnchorSerialize, AnchorDeserialize, Clone)] struct GStruct<T> { data: T, }
the generated idl is fine and can be used. If we do
#[account] struct MyAccount { data: GStruct<MyStruct>, } #[derive(AnchorSerialize, AnchorDeserialize, Clone)] struct GStruct<T> { data: T, } #[derive(AnchorSerialize, AnchorDeserialize, Clone)] struct MyStruct { data: u32, }
the generated idl is unparsable. Might open a PR for this later, but in case I forget wanted to at least have the issue. MRE for this here: https://github.com/cryptopapi997/anchor-generics-mre
The text was updated successfully, but these errors were encountered:
Should be fixed by #3016, feel free to take a look @acheroncrypto
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
The title says it all - if we do:
the generated idl is fine and can be used. If we do
the generated idl is unparsable. Might open a PR for this later, but in case I forget wanted to at least have the issue. MRE for this here: https://github.com/cryptopapi997/anchor-generics-mre
The text was updated successfully, but these errors were encountered: