[ghc-steering-committee] Proposal 34: The INCOMPLETE_CONTEXTS pragma proposal

[Simon Marlow]

+1 from me too.  Needing to add Show constraints when using trace seems
like it might be a problem, but in practice (at least for me) it never has
been.

If it's only a debugging feature, it doesn't help with Eval, either.

On 13 March 2017 at 00:50, Manuel M T Chakravarty <chak at justtesting.org>
wrote:

> +1
>
> > Am 13.03.2017 um 02:52 schrieb Roman Leshchinskiy <
> rleshchinskiy at gmail.com>:
> >
> > Hi,
> >
> > I propose we reject this.
> >
> > Reasons:
> >
> > 1. The motivation is quite weak. In the case of tracing this seems
> > like a rather large hammer for such a small nail. The other examples
> > in the document aren't convincing to me at all. As Simon PJ points
> > out, a wildcard context would handle most of the cases in question.
> >
> > 2. The extension is dangerous, as the proposal itself acknowledges. It
> > explicitly requires that "Hackage should refuse to accept any package
> > upload" with this pragma. To me, this seems like far too much
> > machinery for this (and a lot of people don't use Hackage). A compiler
> > flag might be more reasonable but even then, I don't see the benefits
> > as being worth it.
> >
> > 3. The extension is underspecified. It's not clear to me what the
> > exact semantics are and what an implementation would look like.
> >
> > Thanks,
> >
> > Roman
> > _______________________________________________
> > ghc-steering-committee mailing list
> > ghc-steering-committee at haskell.org
> > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee
>
> _______________________________________________
> ghc-steering-committee mailing list
> ghc-steering-committee at haskell.org
> https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-steering-committee/attachments/20170313/5c653fdf/attachment.html>