Re: Cost Centre MAIN

2010-09-23 Thread Stefan Wehr
2010/9/21 Simon Marlow marlo...@gmail.com: On 19/09/2010 13:11, Stefan Wehr wrote: Hi all, I'm profiling a Haskell program and now getting that the program spents 56% of its individual time in the cost centre MAIN (note the capital letters). I searched the documentation for this cost

Re: Non-exhaustive pattern match(es) warning in lambda functions

2010-09-23 Thread Christian Maeder
Am 22.09.2010 18:05, schrieb Simon Peyton-Jones: Good point. Simon and I have decided we agree. I'll push a patch shortly. For patterns in left hand sides (lhs) of let or where also no warnings are issued. data Foo = Bar Int | Baz test3 :: Foo - Int test3 x = let Bar i = x in i Will or

RE: Non-exhaustive pattern match(es) warning in lambda functions

2010-09-23 Thread Simon Peyton-Jones
| For patterns in left hand sides (lhs) of let or where also no warnings | are issued. | | data Foo = Bar Int | Baz | | test3 :: Foo - Int | test3 x = let Bar i = x in i | | Will or should these cases be covered, too? No, I don't plan to warn about these, which is the case at present. It's

Re: clearing GHCi (and, by extension, hint) loaded module dependencies

2010-09-23 Thread Simon Marlow
On 22/09/2010 01:19, Alex Suraci wrote: On Tue, Sep 21, 2010 at 10:30 AM, Daniel Gorínjcpetru...@gmail.com wrote: Hi What I make of this is that you should run a new interpreter (i.e. use runInterpreter(T)) instead of calling reset. Could you try this this approach and see if it works?

Re: Non-exhaustive pattern match(es) warning in lambda functions

2010-09-23 Thread Christian Maeder
Am 23.09.2010 10:40, schrieb Simon Peyton-Jones: | For patterns in left hand sides (lhs) of let or where also no warnings | are issued. | | data Foo = Bar Int | Baz | | test3 :: Foo - Int | test3 x = let Bar i = x in i | | Will or should these cases be covered, too? No, I don't plan

Re: GHCi 6.12.3 stdout redirection works for :type, but not for :info

2010-09-23 Thread Simon Marlow
On 22/09/2010 18:14, Claus Reinke wrote: good diagnosis. want to make a ticket? done: http://hackage.haskell.org/trac/ghc/ticket/4332 On second thought: is there any reason to use haskelline for *output*, as opposed to *input* history logging/editing? I think we were using Haskeline for