From: zn@...
Date: 2021-02-11T14:39:39+00:00
Subject: [ruby-core:102459] [Ruby master Bug#17505] Can `Thread#group`	actually be `nil`?

Issue #17505 has been updated by znz (Kazuhiro NISHIYAMA).


Just FYI

Japanese documents says
```
������������������������������ nil ������������������
```

Dead thread's group returns `nil` from 1.8.0 to 1.9.0-0.

```
% docker run -it --rm ghcr.io/ruby/all-ruby env ALL_RUBY_SINCE=ruby-1.8 ./all-ruby -e 'th=Thread.start{};Thread.pass;p th.group.class'
ruby-1.8.0            NilClass
...
ruby-1.9.0-0          NilClass
ruby-1.9.0-1          ThreadGroup
...
ruby-3.0.0            ThreadGroup
```

----------------------------------------
Bug #17505: Can `Thread#group` actually be `nil`?
https://bugs.ruby-lang.org/issues/17505#change-90347

* Author: marcandre (Marc-Andre Lafortune)
* Status: Closed
* Priority: Normal
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
Is there a circumstance where `Thread#group` could actually be `nil`?

The documentation says so, there seems to be source code for this, but I can find no test or RubySpec for this and I don't see anywhere in the `ThreadGroup` API that could allow this.




-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>