1 unstable release

0.1.0 Sep 22, 2019

#8 in #pinning

Download history 14/week @ 2024-08-26 2/week @ 2024-09-09 20/week @ 2024-09-23 4/week @ 2024-09-30 10/week @ 2024-10-07 8/week @ 2024-10-14 9/week @ 2024-10-28 20/week @ 2024-11-04 13/week @ 2024-11-18 7/week @ 2024-11-25 7/week @ 2024-12-02 27/week @ 2024-12-09

54 downloads per month
Used in 2 crates

MIT/Apache

12KB
126 lines

ergo-pin

Immobilis ergo pin

Ergonomic stack pinning for Rust.

ergo-pin exports a single proc-macro-attribute #[ergo_pin] that can be applied to a function/block/tt-accepting-macro-invocation to provide the "magical" pin! within the scope. You can consider this pin! macro equivalent to a function with the signature:

extern "bla̴ck̀ mag̸ic͘" fn pin!<T>(t: T) -> Pin<&'local mut T>;

it will take in any value and return a Pin<&mut _> of the value, with the correct local stack lifetime.

Internals

Internally the pin! macro works by injecting extra statements before the statement that contains it to create this Pinned reference, it's probably easiest to see what it's doing by example. Given some code like

#[ergo_pin] {
    quux(pin!(Foo::new().bar()).baz());
}

this will be re-written to

{
    let mut __ergo_pin_0 = Foo::new().bar();
    let __ergo_pin_0 = unsafe {
        ::core::pin::Pin::new_unchecked(&mut __ergo_pin_0)
    };
    quux(__ergo_pin_0.baz());
}

The expression passed to pin! is first bound to a local variable, this is then shadowed by a Pinned reference to itself (you may recognise this from the pin-utils::pin_mut! stack pinning macro), finally the pin! call is replaced with the local variable used.

Since this requires re-writing code outside the macro this can't be implemented by as a normal pin! macro, which is why the main entrypoint is the #[ergo_pin] attribute.

Rust Version Policy

This crate only supports the current stable version of Rust, patch releases may use new features at any time.

License

Licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you shall be dual licensed as above, without any additional terms or conditions.

Dependencies

~1.5MB
~37K SLoC