#2480: error function is not lazy
--------------------------+-------------------------------------------------
Reporter: NeilMitchell | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: Compiler | Version: 6.8.3
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Testcase: cg016 | Architecture: Unknown
Os: Windows |
--------------------------+-------------------------------------------------
Comment (by Isaac Dupree):
well, at least it could be split up into two pieces: the fact that there
is an error, and the contents of the error, if possible. Usually it's
rather useful to know it's not just an infinite loop. Perhaps there is
some way to make two RTS calls, and have the first one put up an "Error"
dialog and the second one (if it ever happens) add the error's contents?
(e.g. `fix error` and `error (fix ('a':))` both cannot have their error
strings serialized.) It might be useful to have a third division, say,
the first 500 characters of the error message, or however many characters
have been successfully generated within, say, 3 seconds of CPU time. Hmm,
seems a bit complicated :-/ but going to an effort to print whatever you
have of the error message will be useful for tracking where it came from
(where the bug is -- which error call it is).
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/2480#comment:3>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
