Matt Parsons

> What is your situation? We currently are running `nixpkgs` for our main and are trying to transition to `haskell.nix` as this will allow us to use `cabal.project` as a...

> My fear, and perhaps the fears of others, is putting work into a patch and then the contribution not being found acceptable. This is absolutely a concern of ours...

I'm in favor of this change. It follows general best practices for `Generic` programming to use standard class behavior instead of propagating `Generic` derived behavior for leaves on the AST.

Very interesting. This definitely speaks to a weakness of `Generically` and `DerivingVia` for deriving classes like this. I think we need to - at least - add documentation to `Generically`...

Yeah, that's very much the same as defining, say, ```haskell newtype ZipList a = ZipList [a] deriving newtype (Functor, Monad) instance Applicative ZipList where pure = ZipList . repeat ZipList...

This would be an easy PR to make -- only requires modifying the fixity declaration. It'd be good to include some test/example usage showing that it does what is expected.

Using `unsafeSqlFunction` is something that's somewhat common to do -- you need to use it for *any* custom-SQL functions you've defined, and for anything that the specific database supports that...

> If so, should it really be? Why not instead catch the exception and format a nice message of your own choosing? The dynamic nature of `SomeException` means that you...