Commit b75d1940 authored by Committed by Ben GamariBrowse files
Be more aggressive when checking constraints for custom type errors.
This fixes #11990. The current rule is simpler than before: if we encounter an unsolved constraint that contains any mentions of properly applied `TypeError`, then we report the type error. If there are multiple `TypeErrors`, then we just report one of them. Reviewers: simonpj, bgamari, austin Reviewed By: simonpj Subscribers: thomie Differential Revision: https://phabricator.haskell.org/D2151 GHC Trac Issues: #11990
Showing with 109 additions and 10 deletions