Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
chshersh opened this issue Apr 4, 2022 · 0 comments
Open

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

chshersh opened this issue Apr 4, 2022 · 0 comments
Labels
question Further information is requested reexport Reexport something new

Comments

@chshersh
Copy link
Contributor

chshersh commented Apr 4, 2022

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 🙂

@chshersh chshersh added question Further information is requested reexport Reexport something new labels Apr 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested reexport Reexport something new
Projects
None yet
Development

No branches or pull requests

1 participant