[m-rev.] diff: double the typecheck ambiguity warning limit

[Zoltan Somogyi]

On Fri, 7 Nov 2014 14:44:17 +1100 (AEDT), Julien Fischer <jfischer at opturion.com> wrote:
> I think we
> can increase this limit on modern machines without undue side effects and doing
> so avoids spurious warnings.

May I ask what code gets these spurious warnings?

I am not opposed to the doubling (I agree with your reason about
why it shouldn't be a problem), but I also don't think it will be
all that much help. Since type ambiguity is an exponential problem,
doubling the limit allows only ONE more source of ambiguity,
such as one extra Xi = no in a module that imports both
bool and maybe. In such cases, the right way to avoid
warnings about hitting the limit is to write *all* such
unifications as Xi = bool.no or Xi = maybe.no, since
it works even what you add several more such
unifications, not just when you add one.

Zoltan.