Vladislav Zavialov

> Under my definition of orphans, they are only possible if both overlapping instances are defined in the same module (a clear and easy to fix error), or if at...

The problem is that the type of `accountTransactions` is polymorphic in its return type: ``` m ([TransactionDetails], Cursor) ``` This means that one of potential instantiations of `m` is `(->)...

`Shell` supports `IO`, which means it supports `IO` exceptions. You can always throw a meaningful exception in case of `ExitFailure` and then catch it a few levels up.

Current Debian stable uses `ghc-7.6.3`: https://packages.debian.org/stable/ghc

Does this do what you want? ``` filterShell :: (a -> Maybe b) -> Shell a -> Shell b filterShell p s = s >>= select . p ```

> But those close couplings exist anyway I don't see it as a reason to solidify this close coupling in yet another way. We should keep it to a minimum...

The fact that CPP is emitted at all (with or without `--ghc`) creates issues. For example, `happy` can't be used as a preprocessor with `-pgmF`. So, ideally, there should be...

@Ericson2314 Before I continue, do you agree with the approach I’m taking here? In particular, is it fine to add a dependency on `pretty`?

@knothed Currently `happy` does not parse the contents of reduction rules, so if you have e.g. `expr ‘+’ expr { $1 + $2 }` it will simply substitute `happy_var_1` and...

Yes. And if we use typed TH, type errors in the reduction rules can be reported in the original source code, not in the generated code.