Upgrade to bytes 1.0.z

[dekellum]

Note as is, this would cause a duplicate, which we would prefer to avoid:

bytes v0.5.6
└── http v0.2.1
    └── hyperx v1.3.0 (/home/david/src/hyperx)

bytes v0.6.0
└── hyperx v1.3.0 (/home/david/src/hyperx)

So for a complete solution this depends on hyperium/http#440

[dekellum]

The proposed change of 9fd6635 makes this more-or-less dependent on hyperium/http#461, or something similar, so I'll wait for that to land.

[dekellum]

hyperium/http#461 didn't land. Quote from deleted comment there:

Its amazingly paranoid and rather lame that using a standard feature of cargo is some how unprovable to work. (I've thoroughly tested it you tested it some as well.) And weirder still, is that the paranoia doesn't extend to duplicates in peoples existing production applications?!?

Oh well, enough said.

---

Closing in favor of #31