chore: prepare tokio 0.2.16 release

[hawkw]

0.2.16 (April 3, 2020)

Fixes

• sync: fix a regression where Mutex, Semaphore, and RwLock futures no
  longer implement Sync (sync: ensure Mutex, RwLock, and Semaphore futures are Send + Sync #2375)
• fs: fix fs::copy not copying file permissions (fs: Copy file permissions #2354)

Added

• time: added deadline method to delay_queue::Expired (Expose time::deplay_queue::Expired::deadline #2300)
• io: added StreamReader (Add StreamReader to io module #2052)

Signed-off-by: Eliza Weisman eliza@buoyant.io

[cuviper]

FYI, a .gdb_history file snuck into the published crate. I think cargo usually only picks git-tracked files, but I don't see a .cargo_vcs_info.json in the package, so maybe you published from a weird path?

[hawkw]

Agh, that's surprising. I published from in the tokio dir in the repository, could that be the problem? Thanks for letting us know.

[cuviper]

I published from in the tokio dir in the repository, could that be the problem?

I think that should be fine -- I publish rayon-core that way and it still gets .cargo_vcs_info.json.