-
Notifications
You must be signed in to change notification settings - Fork 171
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
Switch from pin-project to pin-project-lite #151
Conversation
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.
Thanks @jplatte. It looks good to me 😊
A merge/rebase of master
should fix CI.
Just a small heads up I think I'll merge #156 before this, which might lead to some merge conflicts here. |
Rebased. Also had to switch the new |
tower-http/src/cors.rs
Outdated
@@ -4,7 +4,7 @@ | |||
//! | |||
//! ``` | |||
//! use http::{Request, Response, Method, header}; | |||
//! use hyper::Body; | |||
//! use hypefut: futureBody; |
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.
I guess this needs to be
//! use hypefut: futureBody; | |
//! use hyper::Body; |
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.
Looks like rust-analyzer used some outdated spans when doing updating uses of a field I renamed 😅
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.
huh, that seems like maybe something that deserves an upstream bug report?
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.
Yep thats cool. Thanks!
Head branch was pushed to by a user without write access
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.
this looks good to me; i commented on a couple of minor notes that aren't really blocking.
@jplatte wanna fix the last round of conflicts? Then we can merge 🚀 |
Done. Also added a reference to the exhaustive match feature tracking issue to the first |
Thanks a lot for working on this! |
Fixes #115.
Contains a decent amount of duplicated code, most of which can be removed once rust-lang/rust#51085 is stable. It might be possible to reduce this duplication using a macro (but I'm not sure whether macros are allowed to take the place of entire match arms, rather than just patterns / expressions), if you want I'll look into that.