Skip to content

Think about splitting Push and Pull on INode interface #7

Description

@manofstick

There are circumstances such as in Fork where pull can't be applied, so could control this through splitting off the push functionality. But this would mean I'd have to have a limited functionality container, the equivalent of ValueEnumerable. Not totally out of the question, I was doing something similar with OrderBy before changing tack there, so have the t4 template in git history.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions