Publish release without pin-project (with pin-project-lite)

[peter-lyons-kehl]

Version 0.4.13 still depends on pin-project. But master got rid of it, and uses pin-project-lite only - thank you.

Unfortunately, pin-project pulls old syn 1.0.109. But axum-core -> async-trait uses syn 2.0.5. That means longer build times...

Output of cargo hackerman explain syn on https://github.com/peter-kehl/rusti :

See also cargo hackerman.

Please, consider disecting out and having a pin-project-lite-only release. Otherwise take this as a big "+1" for #722.

[pacak]

Please, consider disecting out and having a pin-project-lite-only release.

FWIW recently pin-project 1.1.1 uses syn 2. All that tower needs to do is to update to use a new version.

[davidpdrsn]

Tower's master branch has breaking changes. So a new release would mean a new major. So first we have to decide on whether to merge other breaking PRs first. We already have an issue for that.

Regarding pin-project, Tower 0.4.x depends on pin-project as

pin-project = { version = "1", optional = true }

here. So a cargo update in your crate should update to pin-project 1.1.1 since that is compatible with pin-project = { version = "1" }

[peter-lyons-kehl]

Thank you David and Michael.

Would it be worth mentioning the use of pin-project = { version = "1.1" }, maybe somewhere at https://docs.rs/tower/latest/tower? If so, I can provide a PR. I understand that it would be temporary (until the next major Tower version), but it could still help.

[davidpdrsn]

I don’t think so. Cargo is gonna automatically pick the latest version of pin-project when you depend on tower and otherwise cargo update should do the trick.

I’ll close this for now but feel free to ask if you have more questions.

[tobz]

FWIW, this wasn't completed in one big fell swoop -- there's multiple PRs responsible -- but pin-project is in fact no longer used / present in tower: it's all pin-project-lite now.