On Mon, Mar 11, 2013 at 9:33 PM, Isaac Dupree
wrote:
> On 03/11/2013 07:04 PM, Simon Peyton-Jones wrote:
>> Aha. It is indeed true that
>>
>> ghc -fdefer-type-errors -w
>>
>> does not suppress the warnings that arise from the type errors;
>> indeed there is no current way to do so. How to do tha
On 13-03-12 04:47 AM, Joachim Breitner wrote:
...
None of these look particularly appealing. Here some ideas to make it
more convenient for the programmer that require changes to GHC and how
it treats packages:
I. It automatically imports _all_ visible Prelude modules. So
base-pur
On Tue, Mar 12, 2013 at 03:58:28PM +0100, Joachim Breitner wrote:
>
> Both have issues: Putting it in file-io will cause everyone to depend on
> file-io
If it ended up there, then we'd presumably encourage people to use
NoImplicitPrelude and import e.g. list functions from Data.List rather
than P
Hi,
Am Dienstag, den 12.03.2013, 14:35 + schrieb Ian Lynagh:
> I think we should avoid getting bogged down in one small detail at this
> stage. If we make the bulk of the changes now then we still have a few
> months to polish the result before it gets effectively frozen by being
> released.
On Tue, Mar 12, 2013 at 09:47:21AM +0100, Joachim Breitner wrote:
>
> This is especially true when the shim packages are less simple to use,
> due to the handling of Prelude.
Just to make sure I am following you, I think you are saying:
Everything would work fine if there was a Prelude in base (
Hi,
Am Montag, den 11.03.2013, 23:45 + schrieb Simon Peyton-Jones:
> | I don’t feel in the position to actually make a call here, or even to cast
> a vote with
> | confidence, but I’m happy to continue summarizing the discussion until a
> | consensus is found. If there is more discussion,
