Skip to content

Delegate access macros? Should they be public? #2996

@rollo-b2c2

Description

@rollo-b2c2

Third party stream combinators are often a pain in the ass to use because forget to put simple accessors like get_ref, get_mut on their structures. Futures has delegate_sink! delegate_access_inner, for this reason: it makes life better.

As I was writing my own combinator, I was repeating this stuff out, and I wondered if it made sense to have them public to encourage people to give their types a wider API?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions