Drastic Prelude changes imminent

[Gershom B]

I think that _if_ there had been a better organized, more clarifying discussion on the scope of BBP earlier (one was promised after Neil raised concerns, but I think it fell by the wayside), then we might not be in this boat.

Now, whatever the “right” thing is eventually, it does feel like we need to apply brakes until people can settle in further. I know people will be disappointed no matter what happens, and they will feel this stuff has moved slowly enough for long enough.

However, without having had that discussion, I don’t see how we can move forward.

The proposal Lennart and Simon have therefore seems good and necessary, save for the issue of how BBP infects Data.List in particular as well. 

I think we should go with it, and _also_ just have Data.List always export the monomorphic functions for now. I recognize that this means even with AlternativePrelude on, people will not get the full niceness of the “BBP experience”. However, it seems as close as we can get, to my mind, without creating greater headaches and issues all around.

We could perhaps also insert a warning encouraging people to import Data.List qualified, either in this GHC of the next release. This would allow BBP to proceed in a relatively breakage-free way in the future without needing to generalize the Data.List module.

Cheers,
Gershom


On January 27, 2015 at 12:14:03 PM, Augustsson, Lennart (lennart.augustsson at sc.com) wrote:
> Perhaps because a lot of people didn't know about it?
> Simon PJ didn't know until we told him on Friday, so I don't think the change has been that  
> well advertised.
>  
> -----Original Message-----
> From: Libraries [mailto:libraries-bounces at haskell.org] On Behalf Of David Feuer  
> Sent: 27 January 2015 17:07
> To: Yitzchak Gale
> Cc: libraries at haskell.org
> Subject: Re: Drastic Prelude changes imminent
>  
> I'm trying to understand why people with (serious, legitimate) concerns about BBP didn't  
> come out of the woodwork until RC2. I fear it's likely that nothing can be done to change  
> this until 7.12 in any case.
>  
> For the record, I'm not a huge fan of the Foldable abstraction myself; I just don't think  
> now is a good time for that discussion.
>  
>  
> This email and any attachments are confidential and may also be privileged. If you are  
> not the intended recipient, please delete all copies and notify the sender immediately.  
> You may wish to refer to the incorporation details of Standard Chartered PLC, Standard  
> Chartered Bank and their subsidiaries at
> http://www.standardchartered.com/en/incorporation-details.html
>  
> Insofar as this communication contains any market commentary, the market commentary  
> has been prepared by a sales and/or trading desk of Standard Chartered Bank or its affiliate.  
> It is not and does not constitute research material, independent research, recommendation  
> or financial advice. Any market commentary is for information purpose only and shall  
> not be relied for any other purpose, and is subject to the relevant disclaimers available  
> at http://wholesalebanking.standardchartered.com/en/utility/Pages/d-mkt.aspx.  
>  
> Please visit http://wholesalebanking.standardchartered.com/en/capabilities/financialmarkets/Pages/doddfrankdisclosures.aspx  
> for important information with respect to derivative products.
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://www.haskell.org/mailman/listinfo/libraries
>