| commit | 4052a3c23a002a7fa935ed3df487fe97d954b0f6 | [log] [tgz] |
|---|---|---|
| author | Andrew Walbran <qwandor@google.com> | Wed Nov 15 11:50:12 2023 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Nov 15 11:50:12 2023 +0000 |
| tree | 570f6d6a8e622c88b6332edf44fa702561b2af53 | |
| parent | 7f63cf62c39b0e0fbee2bcaac6dfd42d5c819e51 [diff] | |
| parent | 95bf4284246554c65ef66a5c6d1f72080410511c [diff] |
Upgrade pin-project to 1.1.3 am: 774e92dc74 am: ccd6cbd505 am: 95bf428424 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/pin-project/+/2829872 Change-Id: Iaf255d2517f34011848cd7de5e4a363508a3181e Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
A crate for safe and ergonomic pin-projection.
Add this to your Cargo.toml:
[dependencies] pin-project = "1"
Compiler support: requires rustc 1.56+
#[pin_project] attribute creates projection types covering all the fields of struct or enum.
use std::pin::Pin; use pin_project::pin_project; #[pin_project] struct Struct<T, U> { #[pin] pinned: T, unpinned: U, } impl<T, U> Struct<T, U> { fn method(self: Pin<&mut Self>) { let this = self.project(); let _: Pin<&mut T> = this.pinned; // Pinned reference to the field let _: &mut U = this.unpinned; // Normal reference to the field } }
code like this will be generated
To use #[pin_project] on enums, you need to name the projection type returned from the method.
use std::pin::Pin; use pin_project::pin_project; #[pin_project(project = EnumProj)] enum Enum<T, U> { Pinned(#[pin] T), Unpinned(U), } impl<T, U> Enum<T, U> { fn method(self: Pin<&mut Self>) { match self.project() { EnumProj::Pinned(x) => { let _: Pin<&mut T> = x; } EnumProj::Unpinned(y) => { let _: &mut U = y; } } } }
code like this will be generated
See #[pin_project] attribute for more details, and see examples directory for more examples and generated code.
Licensed under either of Apache License, Version 2.0 or MIT license at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
