Skip to content

& shadows the same operator in Data.Function in base #24

@miniBill

Description

@miniBill

& is usually reserved for a function of type a -> (a -> b) -> b, but superrecord's & shadows it

Also, because of #17, it's impossible right now (with the hackage version) to just re-export it with a different name.

I understand that changing that name would be a huge breaking change, how about deprecating it and using something else? I'd use &=, but I must admit I haven't surveyed the conventions enough to be confident in my suggestion

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