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
Support zerocopy #325
Comments
We should come up with a strategy for supporting these unstable libraries. I've opened #329 to come up with one. |
Having spent some time trying to make I am working on a general solution to this though so that you can partially "eject" your flags definition and can add derives for libraries |
Thanks for looking into this! |
Thanks for checking this out @qwandor 👍 As per #326 (comment), we can now work with |
As per #310, for users of bitflags to continue being able to derive
zerocopy
traits on bitflags-generated types, it appears that there will need to be a cargo feature flag to make the internal bitflags types derive the relevant zerocopy traits.The text was updated successfully, but these errors were encountered: