Skip to content
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.

Sign up for GitHub

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

Jump to bottom

unsafe_zero_copy #1440

Closed
armaniferrante opened this issue Feb 11, 2022 · 2 comments
Closed

unsafe_zero_copy #1440

armaniferrante opened this issue Feb 11, 2022 · 2 comments
Labels
help wanted Extra attention is needed lang

Comments

@armaniferrante
Copy link
Member

The current implementation of zero copy uses some unsafe trait implementations for Pod and Zeroable. We should change the macro name to reflect this. For example, #[account(unsafe_zero_copy)].
@armaniferrante armaniferrante added help wanted Extra attention is needed lang labels Feb 11, 2022
@johnanthos
Copy link
Contributor

#2330 seems to have made zero_copy safe by default. Should this issue be closed?

@acheroncrypto
Copy link
Collaborator

#2330 seems to have made zero_copy safe by default. Should this issue be closed?

Yes, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Extra attention is needed lang
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@armaniferrante @johnanthos @acheroncrypto