On 04/06/2008, at 10:12 AM, Ronald Guida wrote:
I would ask, how do I examine the evaluation order of my code, but
the answer is already available: use a debugger. Haskell already has
debugging tools that do exactly what I need.
(http://www.haskell.org/haskellwiki/Debugging)
In particular,
Ronald Guida wrote:
[snip]
By default, a lazy language will procrastinate. By default, a strict
language will anticrastinate. Either way, I can waste resources by
blindly accepting the default time management plan.
Nice analysis.
Would you like to put that (the whole thing, not just that
I was looking at the real time queues in [1] and I wanted to see what
would happen if I tried to write one in Haskell. The easy part was
translating the real time queue from [1], p43 into Haskell.
The hard part is testing to see if the rotations really happen what
they should. Basically, I
Ronald Guida wrote:
I was looking at the real time queues in [1] and I wanted to see what
would happen if I tried to write one in Haskell. The easy part was
translating the real time queue from [1], p43 into Haskell.
The hard part is testing to see if the rotations really happen what
they
Don Stewart wrote:
2. Is there any way to systematically search for or detect laziness
leaks?
Profiling, and looking at the Core. Being explicit about the
evaluation strategy you want is a fine idea though.
Albert Y. C. Lai wrote
A true cause of laziness is in accumulating a chain of
On Tue, 2008-06-03 at 20:12 -0400, Ronald Guida wrote:
Don Stewart wrote:
2. Is there any way to systematically search for or detect laziness
leaks?
Profiling, and looking at the Core. Being explicit about the
evaluation strategy you want is a fine idea though.
Albert Y. C. Lai
