On 15/06/2020 19:50, Ben Gamari wrote:
Frankly, this makes me wonder whether we should change the output produced for loops. The current error is essentially un-Googleable, as we see here. I know I have personally struggled with this same issue in the past.
I wholeheartedly agree with this suggestion. Maybe we could even start a little taxonomy of errors by adding an error code
to the message that would be more searchable? Something like E5032? _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
