Upgrading hyper 0.4 to 0.5
Breaking0.4.0 → 0.5.2Breaking6New9Fixed5
BreakingUpgrade verdict
6 breaking changes.
In plain terms
- Code that handles header parsing errors must now deal with hyper::Error rather than the unit type.
- The error type gained new variants, and some header and shared type functions now return a different type, so callers may need updates.
- Response.deconstruct() and construct() now take a &mut Headers instead of the struct proper.
- Users of deref! from the header module must switch to __hyper__deref!.
Must act Top 3 of 6 that need code or config changes
Installs 43 packages in all (was 46).
What you must change
Breaking6
Header components now return hyper::Error instead of (), and the Error enum is extended.
hyper::ErrorExtends the Error enum and changes the return type of header/shared/types.
ErrorResponse.deconstruct() and construct() now take a &mut Headers instead of the struct proper.
Response.deconstruct()Response.construct()HeadersUsers of deref! from the header module must switch to __hyper__deref!.
deref!__hyper__deref!Custom Connectors must change connect to take &self, and Request::with_connector() now takes &NetworkConnector.
connectRequest::with_connector()NetworkConnectorAdding a new required method to a public trait is a breaking change.
NetworkConnectorset_ssl_verifier