-
Notifications
You must be signed in to change notification settings - Fork 686
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
rust: 1.85.0 / edition 2024 #12966
rust: 1.85.0 / edition 2024 #12966
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #12966 +/- ##
==========================================
- Coverage 70.24% 70.22% -0.02%
==========================================
Files 855 855
Lines 176287 176569 +282
Branches 176287 176569 +282
==========================================
+ Hits 123837 124003 +166
- Misses 47296 47406 +110
- Partials 5154 5160 +6
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
There were too many files to take a detailed look at, so just approving to unblock!
It would have been really nice to have the cargo fmt related changes as part of a separate PR from the update :( That was possible according to this doc |
Doesn't splitting up the formatting into its own commit within PR achieve the very same thing? (Admittedly our PR merges squash, but for the purposes of review there isn't a meaningful difference, is there?) |
Formatting style changed so the reviewability of this is non-existent. The first two commits should be roughly reviewable though. Most of the changes are trivial adaptations for edition 2024:
gen
became a reserved keyword, mitigated by using a raw identifierr#gen
;unsafe_on_in_unsafe_fn
became a warning by default which for us is a compilation failure, mitigated by wrapping unsafe operations individually inunsafe {}
(I spent some time to update safety docs at the same time);use<>
annotations;ref
in most places;