You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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 🙂
The text was updated successfully, but these errors were encountered:
base-4.16
started to reexport the unary tuple typeSolo
from theData.Tuple
module. A data type like this one is helpful in various library. I'm usually usingOnly
from theOnly
package in libraries likepostgresql-simple
.Key differences between
Solo
andOnly
:Solo
isdata
andOnly
isnewtype
(I see this as a drawback ofSolo
)Solo
is available without extra dependencies but only since GHC-9.2It's not clear to me whether we should reexport
Solo
. I believe, all other libraries will continue to useOnly
as there's no benefit in switching toSolo
. But still, maybe there're use cases I'm not aware of 🙂The text was updated successfully, but these errors were encountered: