Re: Remove eq and show from num class

2017-09-08 Thread John Wiegley
> "CS" == Carter Schonwald writes: CS> I mostly wanted to confirm that we in fact will actually say yes before CS> doing the formal writtingup :) Ah, I actually misread the English sentence! I though it said "all yays from committee members", and that it was

Re: Remove eq and show from num class

2017-09-08 Thread Bardur Arantsson
On 2017-09-08 13:55, Anthony Clayden wrote: >> This has been how it is in GHC for a long time now, >> so it really is a matter for the Haskell' committee >> rather than one of the GHC committees. > > MPTCs, GADTs (for example) have been in GHC > far longer. AFAIUI these are far from trivial to

Re: Remove eq and show from num class

2017-09-08 Thread Carter Schonwald
I mostly wanted to confirm that we in fact will actually say yes before doing the formal writtingup :) On Fri, Sep 8, 2017 at 2:06 PM, John Wiegley wrote: > > "AC" == Anthony Clayden writes: > > AC> All yays from committee members please

Re: Remove eq and show from num class

2017-09-08 Thread John Wiegley
> "AC" == Anthony Clayden writes: AC> All yays from committee members please reply with yes to this email :) Just to note: I don't recall their being an actual "vote" on this during our informal meeting of just a few of the committee members here at ICFP, so I

Re: Remove eq and show from num class

2017-09-08 Thread Anthony Clayden
> On 8 Sep 2017 at 07:54 Nathan van Doorm wrote: Thank you Nathan and Mario for your explanations. > The motivation is that there are many types with sensible > definitions for addition and multiplication etc that can't > be instances of Eq or Show, for example functions to > numbers (allowing

Re: Remove eq and show from num class

2017-09-08 Thread Anthony Clayden
> On 2017-09-08 at 08:43 AM, Herbert RIedel wrote: Thank you Herbert for the explanation. >> On 2017-09-08 at 09:19:54 +0200, Anthony Clayden wrote: > > [...] > > I can see how the proliferation of committees & github > repos may seem confusing to casual observers, ... Not that so much. I

RE: Remove eq and show from num class

2017-09-08 Thread Simon Peyton Jones via Haskell-prime
Good summary Herbert. It'd be great to have it as a page on haskell.org, rather than just in soon-lost email. Simon | -Original Message- | From: Haskell-prime [mailto:haskell-prime-boun...@haskell.org] On Behalf | Of Herbert Valerio Riedel | Sent: 08 September 2017 09:43 | To: Anthony

Re: Remove eq and show from num class

2017-09-08 Thread Herbert Valerio Riedel
On 2017-09-08 at 09:19:54 +0200, Anthony Clayden wrote: [...] > If this is to the committee, shouldn't it be on the committee list? > (I mean ghc-steering-committee.) > Or is there some other committee? I thought the Haskell-prime forum > and process was dead/replaced by the github proposals

Re: Remove eq and show from num class

2017-09-08 Thread Nathan van Doorn
Anthony, this proposal is to remove the Eq and Show constraints from the Num class. Specific instances of Num, like Int and Float, will still have those instances. This has been how it is in GHC for a long time now, so it really is a matter for the Haskell' committee rather than one of the GHC

Re: Remove eq and show from num class

2017-09-08 Thread Mario Blazevic
On Fri, Sep 8, 2017 at 3:19 AM, Anthony Clayden < anthony_clay...@clear.net.nz> wrote: > I'm baffled. Is this some sort of 'in' joke at ICFP? > Then remember the rest of the world can see this list. > > > All yays from committee members please reply with yes to > this email :) > > If this is to

Re: Remove eq and show from num class

2017-09-08 Thread Anthony Clayden
I'm baffled. Is this some sort of 'in' joke at ICFP? Then remember the rest of the world can see this list. > All yays from committee members please reply with yes to this email :) If this is to the committee, shouldn't it be on the committee list? (I mean ghc-steering-committee.) Or is there

Re: Remove eq and show from num class

2017-09-08 Thread Henrik Nilsson
On 09/08/2017 12:45 AM, Carter Schonwald wrote: please say yes or no. its quite easy with email . i'm not going to write that little proposal if folks wont accept it :) I'd love to see those constraints go. But it is important that the full ramifications are clearly articulated. Best,