Skip to content

Should we reexport 'Solo' from 'Data.Tuple'? #406

Open

Description

@chshersh

base-4.16 started to reexport the unary tuple type Solo from the Data.Tuple module. A data type like this one is helpful in various library. I'm usually using Only from the Only package in libraries like postgresql-simple.

Key differences between Solo and Only:

  • Different names
  • Solo is data and Only is newtype (I see this as a drawback of Solo)
  • Solo is available without extra dependencies but only since GHC-9.2

It's not clear to me whether we should reexport Solo. I believe, all other libraries will continue to use Only as there's no benefit in switching to Solo. But still, maybe there're use cases I'm not aware of 🙂

Activity

  1. added
    questionFurther information is requested
    reexportReexport something new
    on Apr 4, 2022
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

    questionFurther information is requestedreexportReexport something new

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions