Proposal: NoImplicitPreludeImport

[Edward Kmett]

Yes, but that leaves the an objection I have to this proposal requiring me
personally to write an extra 1691 import lines -- based on the contents of
my local development folder, to just get back up to par with the status quo.

As a flag I can turn on in a package to get finer grained control? I'm
totally for it!

As a source of *mandatory* boilerplate at the head of each module? It
doesn't strike me as a good trade-off.


On Tue, May 28, 2013 at 11:52 AM, Ian Lynagh <ian at well-typed.com> wrote:

> On Tue, May 28, 2013 at 11:41:44AM -0400, Edward Kmett wrote:
> > I'm definitely in favor of having the *option* to shut off the import of
> > the Prelude without entangling the notion of overriding all of the
> > desugarings.
> >
> > I do, however, feel that removing the Prelude from base is a rather
> strong
> > step, which hasn't seen much support.
>
> Just to clarify: This proposal is to stop importing the module
> implicitly, not to actually remove the module.
>
>
> Thanks
> Ian
> --
> Ian Lynagh, Haskell Consultant
> Well-Typed LLP, http://www.well-typed.com/
>
> _______________________________________________
> Haskell-prime mailing list
> Haskell-prime at haskell.org
> http://www.haskell.org/mailman/listinfo/haskell-prime
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/haskell-prime/attachments/20130528/6e440d94/attachment.htm>