Skip to content

Value-pinning #4

Description

@Tamschi

Is your feature request related to a problem? Please describe.
There are situations in which it would make sense to pin a value directly in a signal.

Describe the solution you'd like
Ideally, this should take the form of new methods in the accessor traits (as breaking change, ideally with semver-trick) where the receiver has the form self: &Pin<Self> for refcounting handles and self: Pin<&Pin<Self>> for inline signals.
This is blocked on rust-lang/rust#44874.

Describe alternatives you've considered
It's possible to do something similar to this with extension traits for Pin<Self>, but that wouldn't allow other crates to usefully implement these traits. Maybe indirection through an unsafe market trait could work 🤔

Additional context
Add any other context or screenshots about the feature request here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    domain: RustInvolves Rust code.effort: 2Relative effort required. There's no specific unit of measurement.priority: somedayIf you need this, please let me know!state: blockedSomething is blocking action (aside from pure proceedings or missing information).type: featureBrand new functionality, features, pages, workflows, endpoints, etc.work: clearA known solution is (to be) implemented.

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions