Repository navigation
Rename the HttpBody export to Body #2839
Description
Activity
- addedE-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.C-featureCategory: feature. This is adding a new feature.Category: feature. This is adding a new feature.A-bodyArea: body streaming.Area: body streaming.
on May 20, 2022 What would be the advantage in case of import both trait and struct?
The struct will be removed, as detailed in #2345.
Reacted by YuriI am just starting up with Hyper so would like to work on this task (if that's ok). By renaming and exporting the
http_body::Bodytrait as justBody, I assume you are talking about updating the following:Lines 19 to 23 in 84f6ae7
pub use http_body::Body as HttpBody; pub use http_body::SizeHint; pub use self::aggregate::aggregate; pub use self::body::{Body, Sender}; But since the concrete
Bodytype is already exported asBody, wouldn't that cause a conflict? Should I get rid of the concrete type export?Yes, we'd need to finish removing parts of
Body, and renaming that. Then this one would be straightforward.Is there a separate task that I can work on to remove parts of
Body?- added a commit that references this issue
on Aug 26, 2022 This is no longer blocked, since
Bodywas renamed toRecvas a stop-gap (#2963).Reacted by Rajiv Sharma- added a commit that references this issue
on Aug 28, 2022 @seanmonstar Created PR to address this, would appreciate a review to understand if I missed something.
- added a commit that references this issue
on Aug 29, 2022 - added a commit that references this issue
on Aug 29, 2022 - added a commit that references this issue
on Aug 30, 2022
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
When the concrete
Bodystruct is removed, we can export thehttp_body::Bodytrait as justBody.