Closed DeboMac closed 2 years ago
Thanks for describing the problem so accurately, whilst providing a solution to avoid users of these crates having to follow the exact version of dependent crates in their cargo manifests while exposing themselves to surprises.
I think a fix could be applied similarly as done in the linked issue.
Currently, it's impossible to specify such dependencies (even if, in my honest opinion, it's a bit cargo's fault):
because cargo will resolve
hyper-rustls v0.23.0
for the whole project, andhyper-rustls v0.22.1
for google_drive3.Then, it becomes impossible to write:
because it fails with:
Maybe this dependency should be updated, or, like it was done in this issue, the
hyper
and thehyper-rustls
crate should be exposed ?Thank you very much