tree 45fc95439291a5540c74cbddd80fdd2fb2ffb569
parent f765c8f59760b8e899c81a649f5d70f9f7c50f6e
author Carl Lerche <me@carllerche.com> 1520571380 -0800
committer GitHub <noreply@github.com> 1520571380 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJaohP0CRBK7hj4Ov3rIwAAdHIIAFtBg5ok1k/s5USTolkMPzcW
 /UEbZA3fwIk8Nkv0/1o87qm+LLSrFmv8yIMGGHB/eORIYYF+C4q1ps6nKaCih2MH
 804U/xyTLTdobaCuXHdg+slVdIlbn0XmXeRgoqUMCq/JoIZfaxeyQ5+4BpMPEu3C
 EM93fViftOqZistYMM/ip71TWZbZ+hWilGa2PP39GR1YhXoBGuyenQKsTALZhIdU
 V1WLe7xUQ2KuPtIgq4nu9jRPj7T1nc0Jn5S7q38fkYXQDmKFJXlsDojFzmesGsZa
 3pQegHiIOg/qI37ypVo7Gp5OkSmnkBt2Jy/dI+dXXEh2o9M0Q2Y6AezfSpctOoM=
 =UCwB
 -----END PGP SIGNATURE-----
 

Update crate to use Tokio reform internally (#303)

Tokio reform was released as a separate crate (`tokio`). However, the
ecosystem has been split as tokio-core is not compatible with tokio.
Libraries (like hyper) that expose tokio-core as part of the public API
cannot easily switch to tokio as is.

This patch updates tokio-core to use tokio internally. This should help
reduce the friction encountered when users attempt to update their code
bases to tokio.