Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch from pin-project to pin-project-lite #206

Merged
merged 1 commit into from
Mar 1, 2022

Conversation

edmorley
Copy link
Contributor

@edmorley edmorley commented Feb 28, 2022

This is another small step towards reducing the size of bollard's dependency tree :-)

tokio and hyper have both switched from the pin-project crate to the lighter-weight pin-project-lite:
tokio-rs/tokio#1778
hyperium/hyper#2566

This does the same for bollard. For the differences between the two crates, see:
https://docs.rs/pin-project-lite/0.2.8/pin_project_lite/#pin-project-vs-pin-project-lite

Note: The full advantage of this won't be seen until a new hyperlocal release exists that contains:
softprops/hyperlocal#54

...and bollard updates to that release, so that pin-project can be fully dropped from the dependency tree. However this doesn't make things any worse in the meantime, since pin-project-lite is already in bollard's dependency tree via both hyper and tokio.

This is another small step towards reducing the size of bollard's
dependency tree :-)

`tokio` and `hyper` have both switched from `pin-project` crate
to the lighter-weight `pin-project-lite`:
tokio-rs/tokio#1778
hyperium/hyper#2566

This does the same for bollard. For the differences between the
two crates, see:
https://docs.rs/pin-project-lite/0.2.8/pin_project_lite/#pin-project-vs-pin-project-lite

Note: The full advantage of this won't be seen until a new
`hyperlocal` release exists that contains:
softprops/hyperlocal#54

...and bollard updates to that release, so that `pin-project` can be
fully dropped from the dependency tree.
@edmorley
Copy link
Contributor Author

The appveyor CI run failed, but due to a transient networking issue:

Error response from daemon: Get https://mcr.microsoft.com/v2/windows/nanoserver/manifests/sha256:8f78a4a7da4464973a5cd239732626141aec97e69ba3e4023357628630bc1ee2: dial tcp 131.253.33.219:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

However I'm not able to retrigger due to not having permissions. Could someone do the honour? :-)

@fussybeaver
Copy link
Owner

That looks sensible, maybe in future this project will be quicker to compile.

@fussybeaver fussybeaver merged commit 757b07f into fussybeaver:master Mar 1, 2022
@edmorley edmorley deleted the pin-project-lite branch March 1, 2022 11:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants