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" <allber...@gmail.com> wrote:
> On Sun, Oct 19, 2014 at 1:02 PM, David Feuer <david.fe...@gmail.com> > wrote: > >> with a flag -XAllowForbiddenInstancesAndInviteNasalDemons >> > > One could argue this is spelled -XIncoherentInstances.... > > -- > brandon s allbery kf8nh sine nomine > associates > allber...@gmail.com > ballb...@sinenomine.net > unix, openafs, kerberos, infrastructure, xmonad > http://sinenomine.net >
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
