Skip to content

Document unsafety #280

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

Merged
merged 1 commit into from
Jun 1, 2022
Merged

Document unsafety #280

merged 1 commit into from
Jun 1, 2022

Conversation

calebzulawski
Copy link
Member

@calebzulawski calebzulawski commented May 21, 2022

Fixes #173. Clippy no longer crashes on this 🙂

I also made the bitmask traits safe, since implementing them isn't really unsafe. The bitmask conversion functions are themselves safe but contain documented unsafe blocks.

@calebzulawski calebzulawski force-pushed the feature/document-unsafety branch 2 times, most recently from bdf5ec7 to 6202515 Compare May 31, 2022 18:37
@calebzulawski calebzulawski force-pushed the feature/document-unsafety branch from 6202515 to 05c92c7 Compare May 31, 2022 18:44
Copy link
Member

@programmerjake programmerjake left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@calebzulawski calebzulawski merged commit f237f13 into master Jun 1, 2022
@calebzulawski calebzulawski deleted the feature/document-unsafety branch October 17, 2022 00:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Document internal unsafety
2 participants