[ruby-core:26125] Re: [ANN] Ruby Developer's Meeting 20091013

> =E2=86=92 either way, rubyspec will probably be a bottleneck
> * everyone should run rubyspec more often, and report any problems found
> (problems with ruby or rubspec are welcome)

So file failures as bugs? Weren't there like 300 though...


> =E2=86=92 a few cases have been reported in ruby-core, what were they doi=
ng?
> * is there a need for a feature to declare a critical session with a
> block where Timeouts etc are delayed?

I have often considered on this fact:
Thread#raise can interrupt another thread in a critical section within
a finally block.

Ways to get around this would be:
deprecate/remove Thread#raise (yea!)
add ability to have an uninterruptible block

uninterruptible {

  interruptible {

  }

}

Then begin finally would be something like

 Thread.uninterruptable do
   begin
     Thread.interruptable do
       # ...
     end
   rescue
     # ...
   ensure
     # ...
   end
 end

(from http://www.ruby-forum.com/topic/143840#650238)

and/or Thread.delay_interrupt(klass) { ... }

Thanks.
-r