Skip to content
This repository has been archived by the owner on Jan 4, 2023. It is now read-only.

Shield unsafe behind optimized feature #5

Open
vlopes11 opened this issue Oct 22, 2021 · 0 comments · May be fixed by #45
Open

Shield unsafe behind optimized feature #5

vlopes11 opened this issue Oct 22, 2021 · 0 comments · May be fixed by #45
Assignees

Comments

@vlopes11
Copy link
Contributor

Implement a new feature optimized to shield all unsafe usage.

When this feature is on, unsafe is allowed

When this feature is off, we should introduce forbid_unsafe in the root of the library:
src/lib.rs: #![cfg_attr(not(feature = "optimized"), forbid(unsafe_code))]

This means that all functions that use unsafe will have to be reimplemented with their safer (and potentially slower) counterparts

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants