-
Notifications
You must be signed in to change notification settings - Fork 13.4k
rust-intrinsic ABI functions should be unsafe #6370
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
It seems like some of them like The safe ones could be re-exported via a non-unsafe function though, because default |
I would prefer if they were unsafe by default and you could explicitly tag them with |
nominating backwards-compatible |
This seems like it should be a pretty easy change to make, so giving this E-easy. The relevant function to change is |
what, i just had this bug for triage a month ago |
@brson says this is an implementation detail. De-milestoning |
This appears to have been done now, all intrinsics are unsafe. We can explicitly expose safe versions if we need to. |
…valuations, r=llogiq,flip1995 Fix FP in `unnecessary_lazy_evaluations` Fix rust-lang/rust-clippy#6343 changelog: Fix FP in `unnecessary_lazy_evaluations`
They seem to be safe by default now when other foreign ABI's are unsafe.
Reasonable people disagree.
The text was updated successfully, but these errors were encountered: