as discussed in ruby-core, we should probably deprecate Thread#raise since it's dangerous.
#1 Updated by Yukihiro Matsumoto about 3 years ago
Although I admit Thread#raise is dangerous, it's not more dangerous
than other asynchronous events, like signals. And I don't think MRI
cannot remove signals, especially keyboard interrupts, as a real-world
language. So there's no reason to deprecate Thread#raise, despite the
fact we need to reimplement Timeout etc.
|as discussed in ruby-core, we should probably deprecate Thread#raise since it's dangerous.
#2 Updated by Yusuke Endoh about 3 years ago
- Status changed from Open to Rejected
- Assignee set to Koichi Sasada
I agree with matz. Just deprecating Thread#raise does not make sense.
I close this ticket as Rejected.
FYI: Some committers discussed a design of controllable asynchronous
exception at developers' meeting in Akihabara. Ko1 wrote the conclusion
memo in ruby-dev:45341. It is almost based on
Akr's suggestion . I think Ko1 will write it soon in
Yusuke Endoh firstname.lastname@example.org