Re-export http crate

[pbzweihander]

Description

I added pub use http; in lib.rs

Motivation and Context

Since tide heavily depends on http crate, it would be great if we can use http crate without adding to Cargo.toml.

How Has This Been Tested?

I checked via cargo doc that the http crate is re-exported.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[secretfader]

You might want to consider pub use http as a better approach. In Rust 2018, extern crate is unnecessary since dependencies are managed in Cargo.toml.

[yoshuawuyts]

@pbzweihander how are you using the http crate? If there's anything in particular missing from what we're exposing it'd be great to know.

[pbzweihander]

@yoshuawuyts Especially StatusCode. If I want to use with_status of IntoResponse, I have to import StatusCode from http

[secretfader]

I also frequently import the http crate. Usually, I'm creating redirect responses or other functionality that I expect will eventually be implemented in Tide.

Until Tide includes conveniences for all possible responses, exporting http seems like a decent option.

[yoshuawuyts]

Until Tide includes conveniences for all possible responses, exporting http seems like a decent option.

We're thinking of how to reduce the Tide API to just the core parts (#162), so I'm a bit cautious around additions that we know we don't want to keep in the long term.

That said, it does feel like exporting http will almost always remain useful, even if we expose shorthands, so it doesn't seem unreasonable to include this as part of core.