-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Replace usage of mem::uninitialized with MaybeUninit #2532
Copy link
Copy link
Closed
Labels
A-http1Area: HTTP/1 specific.Area: HTTP/1 specific.C-refactorCategory: refactor. This would improve the clarity of internal code.Category: refactor. This would improve the clarity of internal code.E-easyEffort: easy. A task that would be a great starting point for a new contributor.Effort: easy. A task that would be a great starting point for a new contributor.
Metadata
Metadata
Assignees
Labels
A-http1Area: HTTP/1 specific.Area: HTTP/1 specific.C-refactorCategory: refactor. This would improve the clarity of internal code.Category: refactor. This would improve the clarity of internal code.E-easyEffort: easy. A task that would be a great starting point for a new contributor.Effort: easy. A task that would be a great starting point for a new contributor.
When the following comment was added in #1845, hyper's minimum supported rust version was
1.27.0hyper/src/proto/h1/role.rs
Lines 1 to 3 in 4e9a006
which I assume is why
std::mem::MaybeUninit, stabilized in1.36.0, could not be used yet. Today, hyper's MSRV is1.46.0, so it should now be possible to investigate removing the#![allow(deprecated)].