|
Re: [GHC] #367: Infinite loops can hang Concurrent Haskell: msg#00172lang.haskell.glasgow.bugs
#367: Infinite loops can hang Concurrent Haskell ----------------------+----------------------------------------------------- Reporter: simonpj | Owner: nobody Type: bug | Status: assigned Priority: lowest | Milestone: 6.8 Component: Compiler | Version: 6.4.1 Severity: normal | Resolution: None Keywords: | Difficulty: Unknown Testcase: | Architecture: Unknown Os: Unknown | ----------------------+----------------------------------------------------- Changes (by igloo): * milestone: => 6.8 * testcase: => Comment: One reason this is annoying is that it means you can't have a manager thread running code (which you have no reason to believe won't go into an infinite loop or generate an infinite amount of output) with a timeout. For example, lambdabot can't just use something like the timeout function above to ensure its modules don't go into an infinite loop. Another example is not being able to give up and return a bad result if you run out of time in something like the ICFP contest. -- Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/367> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler_______________________________________________ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@xxxxxxxxxxx http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: [GHC] #366: incomplete patterns and GADT, GHC |
|---|---|
| Next by Date: | Re: [GHC] #368: Provide a Java Backend, GHC |
| Previous by Thread: | Re: [GHC] #366: incomplete patterns and GADT, GHC |
| Next by Thread: | Re: [GHC] #368: Provide a Java Backend, GHC |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |