-
Notifications
You must be signed in to change notification settings - Fork 817
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
Migrate lints to use 2024 edition practice of unsafe_op_in_unsafe_fn
#4994
Conversation
Having started down this road, I am now considering resetting this for Justification: the contents of @alex (as you commented on the original PR) - what do you think about partially backing this out? For the main |
I don't feel strongly. Certainly it seems fine to me if we want to start with just doing the pyo3 crate, and then maybe we can consider pyo3-ffi later. |
Some type of network error seems to have killed the windows cross-compilation workflow. 😐 |
Yes, it downloads some build tools. We cache them but they keep getting evicted, will try #4995... |
A bit late but I agree, it's a bit silly for a crate that's all just unsafe. |
I think it has been included in ed37c40. See https://github.com/PyO3/pyo3/blob/ea5adbf90413d524fe89ffe00c4ed6f219dafe09/pyo3-ffi/src/lib.rs#L337C6-L337C34. |
Credit to @jonaspleyer for the work here in #4976, I accidentally closed that PR and now can't push to that branch. (Calling it
main
made it awkward for me to push to, sorry 😬)I added an additional commit which should hopefully fix the MSRV build...