David
Thanks for doing this.
Some comments on the code.
* Use warnTc or addWarnTc, rather than fiddling with mkPlainWarnMsg etc.
* Ditto in checkShouldInst, instead of returning a (Maybe WarnMsg),
just use warnTc inside checkShouldInst.
* Don't use tryTc in tcLookupClassMaybe -- it's a
On 2013-09-03 16:19, Simon Peyton-Jones wrote:
Some comments on the code.
Use warnTc or addWarnTc, rather than fiddling with mkPlainWarnMsg
etc. Ditto in checkShouldInst, instead of returning a (Maybe
WarnMsg), just use warnTc inside checkShouldInst.
Why not just getInstEnvs and
Ryan, can you do one final thing? When you run that program, be sure
to specify `+RTS -Dl` (must be linked with -debug.) This will enable
all the debug output where the linker is concerned. There will be a
few hundred lines just for initialization (based on my machine.) If my
theory is
Excerpts from David Luposchainsky's message of Tue Sep 03 07:40:38 -0700 2013:
I don't see any documentation.
In what sense? More comments, longer function headers? I thought the
names used were clear, with comments giving an overview over longer
sections. (If you're talking about Haddock:
On Mon, Sep 02, 2013 at 07:48:58AM +, Simon Peyton-Jones wrote:
| Which of the language extensions listed in `expectedGhcOnlyExtensions`
| are deemed ready for public consumption in GHC 7.8.1,
Good question. Here's the list with my comments. We need input from Ian. on
RelaxedLayout
From: Simon Peyton-Jones simo...@microsoft.com
To: Edward Z. Yang ezy...@mit.edu, Simon Marlow
marlo...@gmail.com
Cc: ghc-devs@haskell.org ghc-devs@haskell.org
Subject: RE: More windows woe
Message-ID:
Hi,
As I said before, I started running HTTP server using Mio in the real
world. Unfortunately, the daemon is not stable.
After one day or so, the server cannot accept any HTTP requests. No
error messages from the server.
The server is alive. To terminate the server (running in a screen
Kazu, thanks for noticing this! I will try to recreate it on my server as
well.
-Andi
On Tue, Sep 3, 2013 at 5:57 PM, Johan Tibell johan.tib...@gmail.com wrote:
Hi Kazu,
On Tue, Sep 3, 2013 at 2:52 PM, Kazu Yamamoto k...@iij.ad.jp wrote:
Hi,
As I said before, I started running HTTP
Hi Kazu,
What sort of workload was the mighty server under during those 1 or 2 days
while you waited for it to become unresponsive. I.e. was this a production
web server? Or were you generating requests at some frequency or leaving it
mostly idle?
-Andi
On Tue, Sep 3, 2013 at 6:29 PM, Andreas
Hi Andi,
What sort of workload was the mighty server under during those 1 or 2 days
while you waited for it to become unresponsive. I.e. was this a production
web server? Or were you generating requests at some frequency or leaving it
mostly idle?
I ran Mighty on http://mew.org. This is my
10 matches
Mail list logo