-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Deny unsafe operations in unsafe fns in libstd/sync/ #74278
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
Deny unsafe operations in unsafe fns in libstd/sync/ #74278
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect that fixing these may not be worth it -- they look like they're all related to the mpsc module which is essentially abandoned at this point (and there's ongoing experiments in the ecosystem which are looking to replace it).
92acbb2
to
8ec744d
Compare
@poliorcetics Would you be opposed to just closing this? This is currently not quite in the shape that I'd like it to be for merging it and I feel like it would be better to dedicate time elsewhere -- editing the mpsc code is pretty much not viable today due to lack of good reviewers, and so I'd rather not spend time hashing out good safety annotations. |
No problems on my side, go ahead. |
@Mark-Simulacrum I think we should have a PR adding just the unsafe blocks then? @polioretics would you mind filing a PR for that? |
I don't think there's any point to doing so, we can just allow the lint for this module. |
Partial fix of #73904.
This encloses
unsafe
operations inunsafe fn
inlibstd/sync/
.@rustbot modify labels: F-unsafe-block-in-unsafe-fn