relude
relude copied to clipboard
Should we reexport 'Solo' from 'Data.Tuple'?
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.
- https://hackage.haskell.org/package/Only
Key differences between Solo and Only:
- Different names
-
SoloisdataandOnlyisnewtype(I see this as a drawback ofSolo) -
Solois 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 🙂