(More detail available here)
(My specific issue is with apecs-stm, but I am fairly certain the issue is also present in apecs)
The mkWorld function features (among others) mkName "Has", which generates the type constructor Has. This requires me to import Has unqualified. Forcing this decision (whether and how to import certain symbols) on the user seems problematic.
Possible fix: It was suggested (see link above) that expressions like mkName "Has" be replaced with ''Has, which might generate the right symbol automatically. Unfortunately, I cannot guarantee that this would work, since I am not familiar with Template Haskell. I am hoping that someone more experienced can confirm/invalidate this.
(More detail available here) (My specific issue is with
apecs-stm
, but I am fairly certain the issue is also present inapecs
)The
mkWorld
function features (among others)mkName "Has"
, which generates the type constructorHas
. This requires me to importHas
unqualified. Forcing this decision (whether and how to import certain symbols) on the user seems problematic.Possible fix: It was suggested (see link above) that expressions like
mkName "Has"
be replaced with''Has
, which might generate the right symbol automatically. Unfortunately, I cannot guarantee that this would work, since I am not familiar with Template Haskell. I am hoping that someone more experienced can confirm/invalidate this.