[GHC] #3628: exceptions reported to stderr when they propagate past forkIO

[GHC]

#3628: exceptions reported to stderr when they propagate past forkIO
---------------------------------+------------------------------------------
    Reporter:  duncan            |        Owner:                  
        Type:  bug               |       Status:  new             
    Priority:  normal            |    Milestone:  6.14.1          
   Component:  Compiler          |      Version:  6.10.4          
    Severity:  normal            |   Resolution:                  
    Keywords:                    |   Difficulty:  Unknown         
    Testcase:                    |           Os:  Unknown/Multiple
Architecture:  Unknown/Multiple  |  
---------------------------------+------------------------------------------
Comment (by duncan):

 In Erlang (see [Erlang's Exception Handling Revisited
 http://ftp.sunet.se/pub/lang/erlang/workshop/2004/exception.pdf])
 processes can be informed when another process terminates, and that
 includes an exit term or exception.

 Apparently unhandled exceptions that terminate a process are also reported
 to a global error logger service provided by the runtime system. See
 figure 7.

 I'm not sure that any of this really helps.

 It seems to me that we have to decide if exceptions that terminate a
 thread are important or not. If they are then they must be thrown
 somewhere else, if they are not then they can be discarded. Reporting to
 stderr or a windows popup is some kind of intermediate judgement:
 "important enough to annoy the users with but not important enough to
 handle properly".

 Having the thread just die seems ok to me. If people want to be notified
 then they can already do that by adding an exception handler.

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3628#comment:4>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler