On 18 August 2005 16:11, Jake Luck wrote:
One slight annoyance using Haskell is the inability to load modules
with type problems in the interactive environment (i.e. GHCi). When
I have a type error, it would be nice to have an interactive way to
explore what the compiler thinks about the
Hi,
One slight annoyance using Haskell is the inability to load modules
with type problems in the interactive environment (i.e. GHCi). When I
have a type error, it would be nice to have an interactive way to
explore what the compiler thinks about the types involved -- as it is,
I have to resort
One slight annoyance using Haskell is the inability to load modules
with type problems in the interactive environment (i.e. GHCi). When I
have a type error, it would be nice to have an interactive way to
explore what the compiler thinks about the types involved -- as it is,
I have to resort to
Hi Jake,
program. How do most of the folks here debug their large code base?
You might have some success with Hat, http://www.haskell.org/hat/, for
debugging.
Unfortunately unless you are doing Monadic computations, breakpoints
don't really work as well as in strict imperative programs.
I look at the source code and think about it... Generally I code in vi,
then run ghci, or compile and run. I find from experience the type
errors are normally easy to fix, you just look at the error, and study
the structure of the function. If I still have problems I edit the code
to return or
On Thu, 2005-08-18 at 15:17 +0200, Ketil Malde wrote:
Hi,
One slight annoyance using Haskell is the inability to load modules
with type problems in the interactive environment (i.e. GHCi). When I
have a type error, it would be nice to have an interactive way to
explore what the compiler
