On Sun, Feb 9, 2014 at 1:28 PM, Gabriel Gonzalez <[email protected]> wrote: > So I was thinking some more about this, and I was wondering if perhaps the > solution would be to simply explain in the `pipes-parse` tutorial how to > simplify type errors using the trick of defining an intermediate non-lens > function.
I don't know what to prefer anymore, but this one looks like an interesting idea. I should mention that temporarily giving explicit types to expressions in order get more precise type errors is something I do quite often while developing Haskell code, so I'd be happy if we decide to go this way and teach more users how useful this technique is. This same technique is useful when doing “hole-driven development”. Maybe we should try this approach first, as it is the simplest to support. If after a couple of months we continue to get complaints from users encountering these complex error messages, then we can review the decision. Regards, Renzo Carbonara. -- You received this message because you are subscribed to the Google Groups "Haskell Pipes" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected].
