
I read http://www.haskell.org/haskellwiki/Timing_out_computations I thought I saw an issue and tested it: http://hpaste.org/44512/timed_iteration IMO, the timeout function should return the last iterated value when it is signaled, and not the next one after the signal. Is there a convention for this behavior? -- Alex R

http://hpaste.org/44514/timed_iteration_try_2
seems to work but seems inelegant.
On Fri, Mar 4, 2011 at 2:04 PM, Alex Rozenshteyn
I read http://www.haskell.org/haskellwiki/Timing_out_computations I thought I saw an issue and tested it: http://hpaste.org/44512/timed_iteration
IMO, the timeout function should return the last iterated value when it is signaled, and not the next one after the signal.
Is there a convention for this behavior?
-- Alex R
-- Alex R

http://hpaste.org/paste/44514/timed_iteration_try_3#p44516
Using IORefs instead of MVars; seems to work fine and seems conceptually
better.
On Fri, Mar 4, 2011 at 2:22 PM, Alex Rozenshteyn
http://hpaste.org/44514/timed_iteration_try_2
seems to work but seems inelegant.
On Fri, Mar 4, 2011 at 2:04 PM, Alex Rozenshteyn
wrote: I read http://www.haskell.org/haskellwiki/Timing_out_computations I thought I saw an issue and tested it: http://hpaste.org/44512/timed_iteration
IMO, the timeout function should return the last iterated value when it is signaled, and not the next one after the signal.
Is there a convention for this behavior?
-- Alex R
-- Alex R
-- Alex R
participants (1)
-
Alex Rozenshteyn