Alexis King

You have to be *very* careful when using cost center profiling because cost center annotations can prevent compiler optimizations, which rather defeats the purpose. Reading the dumped core can help...

> When profiling, Haskell seems to assign all top level function definitions automatically as Cost Centers, which makes sense. GHC doesn’t add any cost centers automatically by default, but you...

No worries, I certainly understand. I think this project is really exciting, for what it’s worth, and it seems to work pretty well considering how young it is.

Yes, I looked through the source about a week ago and found [this line in `GraphQL.Resolver`](https://github.com/jml/graphql-api/blob/ba407bc8aaa182aa3e98ca0cdce509231e2318ca/src/GraphQL/Resolver.hs#L217): ```haskell instance forall m hg. (HasResolver m hg, Functor m, ToValue (Maybe hg)) =>...

Err, actually, I realized the `FromJSON` instance is probably for use with `servant-client`. In that case, the `FromJSON` instance is obviously necessary, but I think the “right” thing to do...

I’m not fond of any of the solutions involving orphans, especially since it could be extremely confusing if any other libraries want to depend on `servant-checked-exceptions`. I do totally understand...

> However, one small question I have is the following: Does it ever make sense to send back an error with a HTTP 200 response? I personally can't think of...

I realize this is a somewhat old thread, but I, too, am interested in what the current state of things is. The package fragmentation already seems sort of bad—there is...

The irony here is that, after I made the comment with a plea for less fragmentation, I promptly went off and forked this package and rewrote its interface extensively. This...

@spacekitteh My fork is not backwards-compatible because it removes exports from `Control.Monad.Freer`, so a PR with the changes as-is would probably be a bad idea. I could reintroduce the old...