Polymorphism in the Prelude

[Edward Kmett]

* The big issue I have is the one I already mentioned -- the fact that the price is born by every user going forward. You spend a line of boiler plate setting up NoImplicitPrelude, and an import of Prelude.Whatever so all users pay for it forever. The current plan on the other hand has 0 tax for users on an ongoing basis and most of the boilerplate users do have melts away.

* A far less compelling, but tedious technical issue is if you import a bunch of these Foo.Poly modules, on windows (with certain build tools?) with enough modules with the same final name .Poly you can run into linker problems, we've actually had users run into this with lens.

-Edward

> On Jun 16, 2014, at 10:09 AM, Erik Hesselink <hesselink at gmail.com> wrote:
> 
>> On Mon, Jun 16, 2014 at 4:07 PM, Edward Kmett <ekmett at gmail.com> wrote:
>> Having attempted to program with NoImplicitPrelude "in anger", I personally
>> think this fix is worse than the disease and I'm personally -1.
> 
> Out of curiosity, what were the problems you encountered?
> 
> Erik