Fair enough. I did try to convey that in the following sentence about how it at
least enforces representational equality, but I can see how my statement might
be taken as understating the importance of that property.
Sent from my iPhone
> On Mar 24, 2014, at 6:57 PM, Simon Peyton Jones wrote:
Isn't it just the default for ghci?
-Edward
> On Feb 5, 2014, at 12:35 AM, Kazu Yamamoto (山本和彦) wrote:
>
> Hi,
>
> If I understand correctly, NoMonomorphismRestriction is now the
> default for GHC 7.8. I think that its document explicitly describes
> it.
>
> --Kazu
> _
Currently, in all the cases I can think of if the splice generates something
that uses an extension then the module must have that flag turned on.
Sent from my iPhone
> On Nov 6, 2013, at 6:57 AM, Gergely Risko wrote:
>
> On Wed, 6 Nov 2013 10:55:09 +, Simon Peyton-Jones
> writes:
>
>>
A very real problem with making such a class is it basically forces a tension
on any library to make two versions of literally everything.
Consider the case of lens, which makes incredibly aggressive use of such
fmap-likes to put on and take off newtypes and does very little else.
All the combi
I agree with Richard. We're still working up the right way to get this
functionality to work, and sadly the simple solution doesn't cover enough
cases. As I noted during the day, this approach doesn't scale. Let's revert.
-Edward
> On Sep 25, 2013, at 8:38 PM, Richard Eisenberg wrote:
>
> In
StandaloneDeriving always struck me as a really heavyweight way to write those
instances. EmptyDataDecls in many ways should have been in all along while
StandaloneDeriving is a rather peculiar ghc'ism.
I'm personally in favor of just making EmptyDataDecls "work better" here.
-Edward
On Aug 14
