I should bump egg-mode to take advantage of the new release of hyper. This issue collects my thoughts on what it would take.
[ ] Migrate from typed headers to http-style headers
[ ] auth::TwitterOAuth can change its Scheme impl to a Display impl, effectively formatting "OAuth {}" with the contents of fmt_scheme
[ ] ContentType is used to set either url-encoded or json, so i can cut out the mime crate and use the strings directly
[ ] make_future's closure takes the headers, so that would need to take a HeaderMap instead
[ ] the rate-limit parsing uses custom headers, which is the most common consumer of those headers
[ ] Functions no longer need to take a Handle, as the tokio runtime can implicitly use one
[ ] ...how does the tokio runtime work anyway >_> Need to decide how to adjust documentation, whether to build hyper with its tokio runtime re-export, etc
...not sure about what else? Will probably learn more as i start the switch.
I should bump egg-mode to take advantage of the new release of hyper. This issue collects my thoughts on what it would take.
http-style headersauth::TwitterOAuthcan change itsSchemeimpl to aDisplayimpl, effectively formatting"OAuth {}"with the contents offmt_schemeContentTypeis used to set either url-encoded or json, so i can cut out themimecrate and use the strings directlymake_future's closure takes the headers, so that would need to take aHeaderMapinsteadHandle, as the tokio runtime can implicitly use one>_>Need to decide how to adjust documentation, whether to build hyper with its tokio runtime re-export, etc...not sure about what else? Will probably learn more as i start the switch.