Rust updates.
Remove Method.is_empty (it can’t be true).
Rust update.
Fix for grammar changes.
Elide some lifetimes.
Implement Deref<str> for Token.
Change a return type from &Vec<T> to &[T].
Implement PartialEq for Headers.

It’s not necessarily efficient (any typed values without raw
representations will get raw representations created), but it works. It
should probably be considered something for testing purposes only,
really.
Upstream fixes.
unused_qualifications is a bit noisy just at present!

See rust-lang/rust#19102 for more details.
Fun fact: `1np` was two tokens but will be one.
Implement appropriate BorrowFrom stuff for Token.
Update to avoid a deprecation warning.
Update to satisfy rust-phf.
Remove fmt::Unsigned impl as it’s gone.
Update the status code stuff from RFC 2616 days.

This means using RFC 7230 et al. instead of RFC 2616, and also taking
information from IANA’s [Hypertext Transfer Protocol (HTTP) Status Code
Registry](http://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml),
most notably there the addition of links for each status code.

There are a handful of [breaking-change]s here:

- The status class 2xx `Success` is now `Successful`;
- 306 Switch Proxy, `SwitchProxy`, is partially removed, now becoming
  306 (Unused), `Code306`;
- 413 Request Entity Too Large, `RequestEntityTooLarge`, is now
  413 Payload Too Large, `PayloadTooLarge`;
- 414 Request-URI Too Long, `RequestUriTooLong`, is now
  414 URI Too Long, `UriTooLong`;
- 416 Requested Range Not Satisfiable, `RequestedRangeNotSatisfiable`,
  is now 416 Range Not Satisfiable, `RangeNotSatisfiable`;
- 419 Authentication Timeout, `AuthenticationTimeout`, is removed and so
  becomes `Code419`;
- 425 Unordered Collection, `UnorderedCollection`, is removed and so
  becomes `Code425`;
- 451 Unavailable For Legal Reasons, `UnavailableForLegalReasons`, is
  removed as the IETF draft it belonged to expired without replacement;

This brings the `StatusCode` enum in line with the registry, *except*
for the matter of 418 I'm a teapot, `ImATeapot`, which is inexplicably
not assigned in the register (I should try asking them about that), but
it’s such a crucial piece of Internet history and so forth that I can’t
bear to remove it.

For now at least, I’ve kept “(unregistered)” in all the doc comments of
the variants rather than switching it to “Unassigned” or similar as the
Status Code Registry would suggest. Smaller diff, and it’d be pretty
pointless anyway. But 306 remains a special case, “(Unused)”, as it is
in the Registry and RFC 7231, section 6.4.6.

Oh, and the matter about 1xx being invalid in HTTP/2 was reverted in one
of the drafts, 14 or so I think.
rustup
Update metadata.
Yay! Header getters can take &self, not &mut self!

This is achieved by using mucell to make the mutability safe. The
practical effect of it is that we’re using smart references (that is,
types implementing `Deref<T>`) rather than references (`&T`) and clones
(`T where T: Clone`). This is just a teensy bit less efficient all the
time but allows convenient use of `Cow` types so that for various cases
it will actually end up more efficient. But the fact that it doesn’t
need `&mut self` is the really big win. In all, I’m definitely happy.
Ditch the old `make` build approach.