-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Move away from 2015 edition? #3898
Comments
Yeah, we should probably target 2021 as part of 1.0. Thanks for writing this up, I have been meaning to for a while but never got to it. |
Note that doing this may make some backports more involved. |
It looks like JohnTitor/ctest2#48 blocks this. |
@ChrisDenton are you just referring to maintaining both 1.0 and 0.2 at the same time like we do currently? We have a handful of planned changes like this that would make backports worse, it would probably be good to get everything else lined up then do them right before we plan to release 1.0. |
Yes, that's what I was referring to.
Makes sense. |
I have tried to migrate it to 2021 using |
We cherry pick commits from |
We upgraded the MSRV of 0.2 to 1.63, meaning that both |
Right now, the libc crate is at Rust edition 2015. Is there a desire to bump to a newer edition?
That would require a significant amount of changes, such as adding
crate
to paths that being with::
(e.g.,crate::c_int
instead of::c_int
). It would also require types inside anunion
to beCopy
or wrapped in aManuallyDrop
.The text was updated successfully, but these errors were encountered: