Open ysangkok opened 9 months ago
But Haskell allocates in many places, and we still call those functions pure.
Sure, bytestring
is littered with unsafePerformIO
s.
But, there aren't a single unsafePerformIO
in postgresql-libpq
, so the bar of introducing the first one is extremely high.
This function seems pure to me, aside from the allocation that it does. But Haskell allocates in many places, and we still call those functions pure. I don't understand why unescapeBytea must be in IO? What kind of side effects can it perform?