Avoiding the hazards of orphan instances without dependency problems

David Feuer david.feuer at gmail.com
Sun Oct 19 17:13:45 UTC 2014

Although they have the same nasal-demon-inducing effects,
IncoherentInstances and AllowForbiddenInstances would turn off errors that
result from distinct situations. It's possible that one might want to play
with forbidden instances in development, keeping the standard coherence
checks in place, and then modify an imported module later.
On Oct 19, 2014 1:05 PM, "Brandon Allbery" <allbery.b at gmail.com> wrote:

> On Sun, Oct 19, 2014 at 1:02 PM, David Feuer <david.feuer at gmail.com>
> wrote:
>> with a flag -XAllowForbiddenInstancesAndInviteNasalDemons
> One could argue this is spelled -XIncoherentInstances....
> --
> brandon s allbery kf8nh                               sine nomine
> associates
> allbery.b at gmail.com
> ballbery at sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonad
> http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/ghc-devs/attachments/20141019/424dccf6/attachment.html>

More information about the ghc-devs mailing list