| commit | 1b1065cac8994b4b4b9e5f46d087d8a2be5b7eef | [log] [tgz] |
|---|---|---|
| author | James Farrell <[email protected]> | Tue May 21 15:03:55 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Tue May 21 15:03:55 2024 +0000 |
| tree | a1e8ed525c3f431e66084ecdf11eb37fb0b50eb9 | |
| parent | 825d7089f75af9a756ff657a3916f5a8dcc08bbd [diff] | |
| parent | 9a0e713611e3bfeb61099bdb39798f2e81f0d782 [diff] |
Update Android.bp by running cargo_embargo am: 668080a9d9 am: 9a0e713611 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/pin-project-lite/+/3095493 Change-Id: Icfe0aabf2c660c5aca1d5c31025817f504582944 Signed-off-by: Automerger Merge Worker <[email protected]>
A lightweight version of pin-project written with declarative macros.
Add this to your Cargo.toml:
[dependencies] pin-project-lite = "0.2"
Compiler support: requires rustc 1.37+
pin_project! macro creates a projection type covering all the fields of struct.
use std::pin::Pin; use pin_project_lite::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 } }
To use pin_project! on enums, you need to name the projection type returned from the method.
use std::pin::Pin; use pin_project_lite::pin_project; pin_project! { #[project = EnumProj] enum Enum<T, U> { Variant { #[pin] pinned: T, unpinned: U }, } } impl<T, U> Enum<T, U> { fn method(self: Pin<&mut Self>) { match self.project() { EnumProj::Variant { pinned, unpinned } => { let _: Pin<&mut T> = pinned; let _: &mut U = unpinned; } } } }
Here are some similarities and differences compared to pin-project.
pin-project-lite guarantees safety in much the same way as pin-project. Both are completely safe unless you write other unsafe code.
This library does not tackle as expansive of a range of use cases as pin-project does. If your use case is not already covered, please use pin-project.
This is the only reason to use this crate. However, if you already have proc-macro related dependencies in your crate's dependency graph, there is no benefit from using this crate. (Note: There is almost no difference in the amount of code generated between pin-project and pin-project-lite.)
This macro does not handle any invalid input. So error messages are not to be useful in most cases. If you do need useful error messages, then upon error you can pass the same input to pin-project to receive a helpful description of the compile error.
pin-project supports this by UnsafeUnpin. (!Unpin is supported by both pin-project and pin-project-lite.)
pin-project supports this.
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.
