Skip to content

add pin projections to #[pin_data] #75

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

add pin projections to #[pin_data] #75

wants to merge 2 commits into from

Conversation

BennoLossin
Copy link
Member

@BennoLossin BennoLossin commented Jul 23, 2025 •
edited
Loading

cc @Darksonn @nbdd0121

Still missing:

  • fix errors in CI
  • commit message
  • tests
  • changelog
  • example

@BennoLossin BennoLossin mentioned this pull request Jul 24, 2025
Open
3 tasks
@BennoLossin
rename project -> project_this in doctest
67fc903 
The next commit makes the `#[pin_data]` attribute generate a `project`
function that would collide with any existing ones.

Signed-off-by: Benno Lossin <[email protected]>
@BennoLossin BennoLossin force-pushed the dev/pin-projections branch 3 times, most recently from 7312caa to a82c203 Compare August 23, 2025 21:39
@BennoLossin
add pin projections to #[pin_data]
2d69836 
Make the `#[pin_data]` macro generate a `*Projection` struct that holds
either `Pin<&mut Field>` or `&mut Field` for every field of the original
struct. Which version is chosen depends on weather there is a `#[pin]`
or not respectively. Access to this projected version is enabled through
generating `fn project(self: Pin<&mut Self>) -> SelfProjection<'_>`.

Signed-off-by: Benno Lossin <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@BennoLossin