Taylor Fausak

Can I do anything to help move this forward? I really want this feature.

I'm happy to help with this! I want to write a blog post about it too :) https://github.com/tfausak/tfausak.github.io/issues/132

Thanks for the quick response! Let me know if I can do anything to help.

I know next to nothing about garbage collectors, much less optimizing GHC's. I'm not at all familiar with Hasql's internals, so I'll poke around there and see if I can...

Unrelated to the original issue, I had some trouble building this project on my machine. ``` [17 of 42] Compiling Hasql.Core.Loops.Receiver ( library/Hasql/Core/Loops/Receiver.hs, .stack-work/dist/x86_64-osx/Cabal-1.24.2.0/build/Hasql/Core/Loops/Receiver.o ) ghc: panic! (the 'impossible' happened)...

For what it's worth, I have chased the original problem down to this line: https://github.com/nikita-volkov/hasql/blob/65fa1ffe990e8959a63d53ce83886e9887faa79d/library/Hasql/Core/Dispatcher.hs#L57 Abusing STM a little, I can see that both `TMVar`s are empty when it tries...

Great, thanks! Seems like the GHC bug has already been reported: https://ghc.haskell.org/trac/ghc/ticket/14338

Oh, I forgot to mention: This is the error that I see: ``` sh $ cabal test --enable-coverage Error: Internal libraries only supported with per-component builds. Per-component builds were disabled...

Yes, there is a workaround. For posterity, here it is: ``` cabal -- cabal.project.local package * coverage: True library-coverage: True package attoparsec coverage: False library-coverage: False ``` I figured I...

For what it's worth, the ergonomics of the workaround aren't very good. I had hoped that you could put the `package attoparsec` section in your `cabal.project`, then either enable or...