Tracking issue for pin-project 0.4 about pin-project HOT 8 CLOSED

Mention #32 in the documents can be checked off/removed, now that the issue is closed.

from pin-project.

I don't list it as a blocker, but rust-lang/rust#63281 is one of the issues to consider.

from pin-project.

@Aaron1011 thanks 👍

from pin-project.

Published 0.4.0-alpha.1 (crate.io, releases, docs)!

from pin-project.

UPDATE: Replaced with #89

TR; DR: Added "Whether or not self: &mut Pin<&mut Self> stabilizes in Rust 1.39" (rust-lang/rust#64325) to blocker list.

rust-lang/rust#64325 stabilizes self: &mut Pin<&mut Self>.
This removes some of the hacks introduced in #47.
It can also solve some existing problems (e.g., tower-rs/tower#326 (comment)).

However, this means will take a different approach between versions prior to 1.39 and versions 1.39 or later. This should not break compatibility, but it will cause a feature that is "supported only with rust 1.39 or later". Specifically, it is a feature that "project/project_into method can be called outside the defined scope" that is planned to be provided by #80.

Also, if stabilization is delayed, the impact on crate using async / await (e.g., tower) is too big, so merge #80 to make those features available in versions 1.39 and earlier.

from pin-project.

Resolved #26 and added "Change the argument type of project method back to self: Pin<&mut Self>" (#89) to unresolved issue list.

from pin-project.

I have filed #107 to fix #102. Once #107 is merged, I will release 0.4.0. As documentation fixes are no breaking changes, will be fixed in the patch versions.

from pin-project.

Published 0.4.0. Thanks everybody for your contribution and feedback (especially @Aaron1011!).

from pin-project.