[ruby-core:101093] [Ruby master Misc#17346] DevelopersMeeting20201210Japan

[ruby-core:101093] [Ruby master Misc#17346] DevelopersMeeting20201210Japan

[mame]

Issue #17346 has been reported by mame (Yusuke Endoh).

----------------------------------------
Misc #17346: DevelopersMeeting20201210Japan
https://bugs.ruby-lang.org/issues/17346

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2020/12/10 13:00-17:00**
Place/Sign-up/Agenda/Log: *TBD*

- Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker.
- Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
- Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
- We will write a log about the discussion to a file or to each ticket in English.
- All activities are best-effort (keep in mind that most of us are volunteer developers).
- The date, time and place are scheduled according to when/where we can reserve Matz's time.
- *DO NOT* discuss then on this ticket, please.

# Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

```
* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)
```

Example:

```
* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
  * I feel this feature is very useful and some people say :+1: so let discuss this feature.
```

- Comment deadline: 2020/12/03 (one week before the meeting)
- The format is strict.  We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86).  We may ignore a comment that does not follow the format.
- Your comment is mandatory.  We cannot read all discussion of the ticket in a limited time.




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

[ruby-core:101125] [Ruby master Misc#17346] DevelopersMeeting20201210Japan

[eregontp]

Issue #17346 has been updated by Eregon (Benoit Daloze).


* [Feature #17351] Deprecate Random::DEFAULT (eregon)
  * Is it OK?

----------------------------------------
Misc #17346: DevelopersMeeting20201210Japan
https://bugs.ruby-lang.org/issues/17346#change-88805

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2020/12/10 13:00-17:00**
Place/Sign-up/Agenda/Log: *TBD*

- Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker.
- Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
- Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
- We will write a log about the discussion to a file or to each ticket in English.
- All activities are best-effort (keep in mind that most of us are volunteer developers).
- The date, time and place are scheduled according to when/where we can reserve Matz's time.
- *DO NOT* discuss then on this ticket, please.

# Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

```
* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)
```

Example:

```
* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
  * I feel this feature is very useful and some people say :+1: so let discuss this feature.
```

- Comment deadline: 2020/12/03 (one week before the meeting)
- The format is strict.  We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86).  We may ignore a comment that does not follow the format.
- Your comment is mandatory.  We cannot read all discussion of the ticket in a limited time.




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

[ruby-core:101208] [Ruby master Misc#17346] DevelopersMeeting20201210Japan

[merch-redmine]

Issue #17346 has been updated by jeremyevans0 (Jeremy Evans).


* [Feature #17055] Allow suppressing uninitialized instance variable and method redefined verbose mode warnings (jeremyevans0)
  * Can we completely remove uninitialized instance variable warnings?  Then we don't need this feature. I would very much like that in Ruby 3.
* [Bug #17280] Dir.glob with FNM_DOTMATCH matches ".." and "." and results in duplicated entries (jeremyevans0)
  * Do we want to change the behavior to exclude ".." and duplicate results?
  * If so, is the pull request acceptable?
* [Bug #17162] Dir['**/*'] : stack smashing detected when listing big amount of directories (jeremyevans0)
  * Do we want to add an internal recursion limit to try to prevent this?
* [Bug #17218] Range#step sometimes behaves unexpectedly with Rational endpoints and increment (jeremyevans0)
  * This is caused by calling `rb_int_*` functions directly instead of Ruby methods.
  * Do we want to switch `arith_seq_last` to using Ruby methods, and if so, should all of the `rb_int_*` be switched, or just the minimal number?
  * The pull request only changes three of the `rb_int_*` to `rb_funcall`, is it OK? 
* [Bug #13663] `String#upto` doesn't work as expected (jeremyevans0)
  * I think the current behavior of `String#upto` in this case is expected and not a bug.
  * Is it OK to close this?


----------------------------------------
Misc #17346: DevelopersMeeting20201210Japan
https://bugs.ruby-lang.org/issues/17346#change-88892

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2020/12/10 13:00-17:00**
Place/Sign-up/Agenda/Log: *TBD*

- Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker.
- Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
- Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
- We will write a log about the discussion to a file or to each ticket in English.
- All activities are best-effort (keep in mind that most of us are volunteer developers).
- The date, time and place are scheduled according to when/where we can reserve Matz's time.
- *DO NOT* discuss then on this ticket, please.

# Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

```
* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)
```

Example:

```
* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
  * I feel this feature is very useful and some people say :+1: so let discuss this feature.
```

- Comment deadline: 2020/12/03 (one week before the meeting)
- The format is strict.  We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86).  We may ignore a comment that does not follow the format.
- Your comment is mandatory.  We cannot read all discussion of the ticket in a limited time.




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

[ruby-core:101210] [Ruby master Misc#17346] DevelopersMeeting20201210Japan

[hunter_spawn]

Issue #17346 has been updated by MaxLap (Maxime Lapointe).


* [Feature #17342] Add Hash#fetch_set (maxlap)
  * Yes/no?


----------------------------------------
Misc #17346: DevelopersMeeting20201210Japan
https://bugs.ruby-lang.org/issues/17346#change-88895

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2020/12/10 13:00-17:00**
Place/Sign-up/Agenda/Log: *TBD*

- Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker.
- Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
- Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
- We will write a log about the discussion to a file or to each ticket in English.
- All activities are best-effort (keep in mind that most of us are volunteer developers).
- The date, time and place are scheduled according to when/where we can reserve Matz's time.
- *DO NOT* discuss then on this ticket, please.

# Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

```
* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)
```

Example:

```
* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
  * I feel this feature is very useful and some people say :+1: so let discuss this feature.
```

- Comment deadline: 2020/12/03 (one week before the meeting)
- The format is strict.  We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86).  We may ignore a comment that does not follow the format.
- Your comment is mandatory.  We cannot read all discussion of the ticket in a limited time.




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

[ruby-core:101215] [Ruby master Misc#17346] DevelopersMeeting20201210Japan

[zn]

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


* [Feature #17361] lambda(&block) does not warn with lazy proc allocation (znz)
  * optimization affects warnings


----------------------------------------
Misc #17346: DevelopersMeeting20201210Japan
https://bugs.ruby-lang.org/issues/17346#change-88899

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2020/12/10 13:00-17:00**
Place/Sign-up/Agenda/Log: *TBD*

- Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker.
- Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
- Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
- We will write a log about the discussion to a file or to each ticket in English.
- All activities are best-effort (keep in mind that most of us are volunteer developers).
- The date, time and place are scheduled according to when/where we can reserve Matz's time.
- *DO NOT* discuss then on this ticket, please.

# Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

```
* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)
```

Example:

```
* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
  * I feel this feature is very useful and some people say :+1: so let discuss this feature.
```

- Comment deadline: 2020/12/03 (one week before the meeting)
- The format is strict.  We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86).  We may ignore a comment that does not follow the format.
- Your comment is mandatory.  We cannot read all discussion of the ticket in a limited time.




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

[ruby-core:101216] [Ruby master Misc#17346] DevelopersMeeting20201210Japan

[marcandre-ruby-core]

Issue #17346 has been updated by marcandre (Marc-Andre Lafortune).


* [Feature #17314] Method declarations (marcandre)
  * Have `Module#protected`, `private`, `public` accept a single Array argument of symbols (and also `private_class_method/public_class_method` for consistency)
  * Have `Module#attr_reader`, `attr_writer`, `attr_accessor` return an array of the method newly defined methods instead of `nil`
  * Have `Module#alias_method` return the symbol of the method defined instead of the receiver
  * Notes: All points are related but not dependant and are requested separately. `Forwardable#def_delegators` and `ActiveSupport`'s `delegate` already return array of symbols


----------------------------------------
Misc #17346: DevelopersMeeting20201210Japan
https://bugs.ruby-lang.org/issues/17346#change-88900

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2020/12/10 13:00-17:00**
Place/Sign-up/Agenda/Log: *TBD*

- Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker.
- Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
- Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
- We will write a log about the discussion to a file or to each ticket in English.
- All activities are best-effort (keep in mind that most of us are volunteer developers).
- The date, time and place are scheduled according to when/where we can reserve Matz's time.
- *DO NOT* discuss then on this ticket, please.

# Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

```
* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)
```

Example:

```
* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
  * I feel this feature is very useful and some people say :+1: so let discuss this feature.
```

- Comment deadline: 2020/12/03 (one week before the meeting)
- The format is strict.  We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86).  We may ignore a comment that does not follow the format.
- Your comment is mandatory.  We cannot read all discussion of the ticket in a limited time.




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

[ruby-core:101218] [Ruby master Misc#17346] DevelopersMeeting20201210Japan

[marcandre-ruby-core]

Issue #17346 has been updated by marcandre (Marc-Andre Lafortune).


* [Feature #17363] Timeouts (marcandre)
  * Add `timeout` parameter to `Queue.pop`, `Ractor.receive`, ...
  * And/or `Timeout::wake` that would make these operations safer by raising only if thread is asleep (and presumably in a safe state)

----------------------------------------
Misc #17346: DevelopersMeeting20201210Japan
https://bugs.ruby-lang.org/issues/17346#change-88901

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2020/12/10 13:00-17:00**
Place/Sign-up/Agenda/Log: *TBD*

- Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker.
- Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
- Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
- We will write a log about the discussion to a file or to each ticket in English.
- All activities are best-effort (keep in mind that most of us are volunteer developers).
- The date, time and place are scheduled according to when/where we can reserve Matz's time.
- *DO NOT* discuss then on this ticket, please.

# Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

```
* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)
```

Example:

```
* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
  * I feel this feature is very useful and some people say :+1: so let discuss this feature.
```

- Comment deadline: 2020/12/03 (one week before the meeting)
- The format is strict.  We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86).  We may ignore a comment that does not follow the format.
- Your comment is mandatory.  We cannot read all discussion of the ticket in a limited time.




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

[ruby-core:101219] [Ruby master Misc#17346] DevelopersMeeting20201210Japan

[marcandre-ruby-core]

Issue #17346 has been updated by marcandre (Marc-Andre Lafortune).


* Meta: please change future deadlines from a week before the meetings to 1 or 2 days before (marcandre)

----------------------------------------
Misc #17346: DevelopersMeeting20201210Japan
https://bugs.ruby-lang.org/issues/17346#change-88902

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2020/12/10 13:00-17:00**
Place/Sign-up/Agenda/Log: *TBD*

- Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker.
- Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
- Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
- We will write a log about the discussion to a file or to each ticket in English.
- All activities are best-effort (keep in mind that most of us are volunteer developers).
- The date, time and place are scheduled according to when/where we can reserve Matz's time.
- *DO NOT* discuss then on this ticket, please.

# Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

```
* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)
```

Example:

```
* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
  * I feel this feature is very useful and some people say :+1: so let discuss this feature.
```

- Comment deadline: 2020/12/03 (one week before the meeting)
- The format is strict.  We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86).  We may ignore a comment that does not follow the format.
- Your comment is mandatory.  We cannot read all discussion of the ticket in a limited time.




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

[ruby-core:101234] [Ruby master Misc#17346] DevelopersMeeting20201210Japan

[marcandre-ruby-core]

Issue #17346 has been updated by marcandre (Marc-Andre Lafortune).


* [Feature #3830] Have a way to distinguish `nil` from closed queue in `Queue.pop` (marcandre)
  * Adding block form similar to `fetch` ok?

----------------------------------------
Misc #17346: DevelopersMeeting20201210Japan
https://bugs.ruby-lang.org/issues/17346#change-88914

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2020/12/10 13:00-17:00**
Place/Sign-up/Agenda/Log: *TBD*

- Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker.
- Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
- Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
- We will write a log about the discussion to a file or to each ticket in English.
- All activities are best-effort (keep in mind that most of us are volunteer developers).
- The date, time and place are scheduled according to when/where we can reserve Matz's time.
- *DO NOT* discuss then on this ticket, please.

# Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

```
* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)
```

Example:

```
* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
  * I feel this feature is very useful and some people say :+1: so let discuss this feature.
```

- Comment deadline: 2020/12/03 (one week before the meeting)
- The format is strict.  We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86).  We may ignore a comment that does not follow the format.
- Your comment is mandatory.  We cannot read all discussion of the ticket in a limited time.




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

[ruby-core:101263] [Ruby master Misc#17346] DevelopersMeeting20201210Japan

[kazuki]

Issue #17346 has been updated by ktsj (Kazuki Tsujimoto).


* [Feature #17371] Reintroduce `expr in pat` (ktsj)
   * Is it OK?

----------------------------------------
Misc #17346: DevelopersMeeting20201210Japan
https://bugs.ruby-lang.org/issues/17346#change-88944

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2020/12/10 13:00-17:00**
Place/Sign-up/Agenda/Log: *TBD*

- Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker.
- Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
- Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
- We will write a log about the discussion to a file or to each ticket in English.
- All activities are best-effort (keep in mind that most of us are volunteer developers).
- The date, time and place are scheduled according to when/where we can reserve Matz's time.
- *DO NOT* discuss then on this ticket, please.

# Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

```
* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)
```

Example:

```
* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
  * I feel this feature is very useful and some people say :+1: so let discuss this feature.
```

- Comment deadline: 2020/12/03 (one week before the meeting)
- The format is strict.  We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86).  We may ignore a comment that does not follow the format.
- Your comment is mandatory.  We cannot read all discussion of the ticket in a limited time.




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

[ruby-core:101266] [Ruby master Misc#17346] DevelopersMeeting20201210Japan

[connor.james.shea]

Issue #17346 has been updated by connorshea (Connor Shea).


- [Feature #15975] Add `Enumerable#pluck` method
  - It pulls values out of an array of hashes (e.g. array of user hashes, `users.pluck(:username)` gets all their usernames)
  - Please reconsider adding the method. I've added a comment to the issue with an example of when it'd be useful for me.
  - Is matz opposed to the method existing at all, or just the name?

----------------------------------------
Misc #17346: DevelopersMeeting20201210Japan
https://bugs.ruby-lang.org/issues/17346#change-88946

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2020/12/10 13:00-17:00**
Place/Sign-up/Agenda/Log: *TBD*

- Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker.
- Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
- Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
- We will write a log about the discussion to a file or to each ticket in English.
- All activities are best-effort (keep in mind that most of us are volunteer developers).
- The date, time and place are scheduled according to when/where we can reserve Matz's time.
- *DO NOT* discuss then on this ticket, please.

# Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

```
* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)
```

Example:

```
* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
  * I feel this feature is very useful and some people say :+1: so let discuss this feature.
```

- Comment deadline: 2020/12/03 (one week before the meeting)
- The format is strict.  We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86).  We may ignore a comment that does not follow the format.
- Your comment is mandatory.  We cannot read all discussion of the ticket in a limited time.




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

[ruby-core:101267] [Ruby master Misc#17346] DevelopersMeeting20201210Japan

[larskanis]

Issue #17346 has been updated by larskanis (Lars Kanis).


* [Feature #12650 and #16604] Use UTF-8 for `ENV` and `Encoding.default_external` on Windows (larskanis)
  * Both have been postponed to ruby-3.0 years ago
  * `default_external = UTF-8` is already de facto standard


----------------------------------------
Misc #17346: DevelopersMeeting20201210Japan
https://bugs.ruby-lang.org/issues/17346#change-88947

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2020/12/10 13:00-17:00**
Place/Sign-up/Agenda/Log: *TBD*

- Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker.
- Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
- Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
- We will write a log about the discussion to a file or to each ticket in English.
- All activities are best-effort (keep in mind that most of us are volunteer developers).
- The date, time and place are scheduled according to when/where we can reserve Matz's time.
- *DO NOT* discuss then on this ticket, please.

# Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

```
* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)
```

Example:

```
* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
  * I feel this feature is very useful and some people say :+1: so let discuss this feature.
```

- Comment deadline: 2020/12/03 (one week before the meeting)
- The format is strict.  We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86).  We may ignore a comment that does not follow the format.
- Your comment is mandatory.  We cannot read all discussion of the ticket in a limited time.




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

[ruby-core:101270] [Ruby master Misc#17346] DevelopersMeeting20201210Japan

[marcandre-ruby-core]

Issue #17346 has been updated by marcandre (Marc-Andre Lafortune).


* [Feature #17365] Adding `channel` to Ractor push api (marcandre)
  * yes/no?
* [Feature #17323] Ractor-local storage (marcandre)
  * What API to use?

----------------------------------------
Misc #17346: DevelopersMeeting20201210Japan
https://bugs.ruby-lang.org/issues/17346#change-88950

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2020/12/10 13:00-17:00**
Place/Sign-up/Agenda/Log: *TBD*

- Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker.
- Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
- Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
- We will write a log about the discussion to a file or to each ticket in English.
- All activities are best-effort (keep in mind that most of us are volunteer developers).
- The date, time and place are scheduled according to when/where we can reserve Matz's time.
- *DO NOT* discuss then on this ticket, please.

# Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

```
* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)
```

Example:

```
* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
  * I feel this feature is very useful and some people say :+1: so let discuss this feature.
```

- Comment deadline: 2020/12/03 (one week before the meeting)
- The format is strict.  We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86).  We may ignore a comment that does not follow the format.
- Your comment is mandatory.  We cannot read all discussion of the ticket in a limited time.




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

[ruby-core:101289] [Ruby master Misc#17346] DevelopersMeeting20201210Japan

[jonathan]

Issue #17346 has been updated by jonathanhefner (Jonathan Hefner).


* [Bug #15661] Disallow concurrent Dir.chdir with block (jonathanhefner)
  * This change is causing some issues in Rails (e.g. https://github.com/rails/rails/commit/ae5ecfe26c8 and https://github.com/rails/rails/issues/40756).
  * I have proposed an "escape hatch" mechanism in https://bugs.ruby-lang.org/issues/15661#note-15.  Summary: wait until the end of the initial `chdir` block to check and raise error.
  * Can this be addressed for Ruby 3.0?


----------------------------------------
Misc #17346: DevelopersMeeting20201210Japan
https://bugs.ruby-lang.org/issues/17346#change-88973

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2020/12/10 13:00-17:00**
Place/Sign-up/Agenda/Log: *TBD*

- Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker.
- Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
- Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
- We will write a log about the discussion to a file or to each ticket in English.
- All activities are best-effort (keep in mind that most of us are volunteer developers).
- The date, time and place are scheduled according to when/where we can reserve Matz's time.
- *DO NOT* discuss then on this ticket, please.

# Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

```
* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)
```

Example:

```
* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
  * I feel this feature is very useful and some people say :+1: so let discuss this feature.
```

- Comment deadline: 2020/12/03 (one week before the meeting)
- The format is strict.  We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86).  We may ignore a comment that does not follow the format.
- Your comment is mandatory.  We cannot read all discussion of the ticket in a limited time.




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

[ruby-core:101312] [Ruby master Misc#17346] DevelopersMeeting20201210Japan

[naruse]

Issue #17346 has been updated by naruse (Yui NARUSE).


* [Misc #17376] Reduce GitHub Actions

----------------------------------------
Misc #17346: DevelopersMeeting20201210Japan
https://bugs.ruby-lang.org/issues/17346#change-89006

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2020/12/10 13:00-17:00**
Place/Sign-up/Agenda/Log: *TBD*

- Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker.
- Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
- Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
- We will write a log about the discussion to a file or to each ticket in English.
- All activities are best-effort (keep in mind that most of us are volunteer developers).
- The date, time and place are scheduled according to when/where we can reserve Matz's time.
- *DO NOT* discuss then on this ticket, please.

# Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

```
* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)
```

Example:

```
* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
  * I feel this feature is very useful and some people say :+1: so let discuss this feature.
```

- Comment deadline: 2020/12/03 (one week before the meeting)
- The format is strict.  We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86).  We may ignore a comment that does not follow the format.
- Your comment is mandatory.  We cannot read all discussion of the ticket in a limited time.




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

[ruby-core:101327] [Ruby master Misc#17346] DevelopersMeeting20201210Japan

[marcandre-ruby-core]

Issue #17346 has been updated by marcandre (Marc-Andre Lafortune).


* [Feature #17380] Useful `include/prepend` in `refine` (marcandre)
  * yes/no?


----------------------------------------
Misc #17346: DevelopersMeeting20201210Japan
https://bugs.ruby-lang.org/issues/17346#change-89024

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2020/12/10 13:00-17:00**
Place/Sign-up/Agenda/Log: *TBD*

- Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker.
- Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
- Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
- We will write a log about the discussion to a file or to each ticket in English.
- All activities are best-effort (keep in mind that most of us are volunteer developers).
- The date, time and place are scheduled according to when/where we can reserve Matz's time.
- *DO NOT* discuss then on this ticket, please.

# Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

```
* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)
```

Example:

```
* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
  * I feel this feature is very useful and some people say :+1: so let discuss this feature.
```

- Comment deadline: 2020/12/03 (one week before the meeting)
- The format is strict.  We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86).  We may ignore a comment that does not follow the format.
- Your comment is mandatory.  We cannot read all discussion of the ticket in a limited time.




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

[ruby-core:101328] [Ruby master Misc#17346] DevelopersMeeting20201210Japan

[takashikkbn]

Issue #17346 has been updated by k0kubun (Takashi Kokubun).


* [Feature #16806] Struct#initialize accepts keyword arguments too by default (k0kubun)
  * Is there any update on kwargs since [the last discussion](https://github.com/ruby/dev-meeting-log/blob/master/DevelopersMeeting20200514Japan.md#feature-16806-structinitialize-accepts-keyword-arguments-too-by-default-k0kubun)? Can we introduce a warning for it in 3.0?

----------------------------------------
Misc #17346: DevelopersMeeting20201210Japan
https://bugs.ruby-lang.org/issues/17346#change-89025

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2020/12/10 13:00-17:00**
Place/Sign-up/Agenda/Log: *TBD*

- Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker.
- Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
- Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
- We will write a log about the discussion to a file or to each ticket in English.
- All activities are best-effort (keep in mind that most of us are volunteer developers).
- The date, time and place are scheduled according to when/where we can reserve Matz's time.
- *DO NOT* discuss then on this ticket, please.

# Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

```
* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)
```

Example:

```
* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
  * I feel this feature is very useful and some people say :+1: so let discuss this feature.
```

- Comment deadline: 2020/12/03 (one week before the meeting)
- The format is strict.  We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86).  We may ignore a comment that does not follow the format.
- Your comment is mandatory.  We cannot read all discussion of the ticket in a limited time.




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