-
-
Notifications
You must be signed in to change notification settings - Fork 113
Changes needed for rust 2024 edition #1635
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
base: main
Are you sure you want to change the base?
Conversation
|
Does this continue to compile without warnings (and clippy lints) with 1.80? |
|
Libadwaita-rs: Yes, gtk4-rs: Not even close. |
|
Then we can't really merge this until we update our MSRV to 1.85 |
That happened (1.86) |
5f7dcbc to
9862644
Compare
|
I tested the current state against gtk4-rs and gtk-rs-core. They pass respectively, when edition = 2021. There was a warning: on manual code though. When using edition 2024, gtk4-rs builds with warnings and gtk-rs-core throws enough warnings to fill the terminal and I cannot say whether they are all restricted to manual code. When it comes to libadwaita-rs passes with both editions with unrelated warnings. |
|
In any case, I think we want to avoid requiring applications to use edition 2024. At least 2021 should also work for applications, ideally also 2018 still. |
|
Applications can choose whichever edition they want. I have all my apps using 2024 atm. This just allows the bindings themselves to use this edition. |
These were tested with https://gitlab.gnome.org/World/Rust/libadwaita-rs/-/merge_requests/94 and it solves the remaining issues. There are more changes that are likely needed. This would benefit from gtk-rs/gtk-rs-core#1663.