* [ruby-core:100206] [Ruby master Misc#17200] DevelopersMeeting20201026Japan
@ 2020-09-28 23:24 mame
2020-10-01 13:34 ` [ruby-core:100256] " finch.parker
` (16 more replies)
0 siblings, 17 replies; 18+ messages in thread
From: mame @ 2020-09-28 23:24 UTC (permalink / raw)
To: ruby-core
Issue #17200 has been reported by mame (Yusuke Endoh).
----------------------------------------
Misc #17200: DevelopersMeeting20201026Japan
https://bugs.ruby-lang.org/issues/17200
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2020/10/26 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/10/19 (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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:100256] [Ruby master Misc#17200] DevelopersMeeting20201026Japan
2020-09-28 23:24 [ruby-core:100206] [Ruby master Misc#17200] DevelopersMeeting20201026Japan mame
@ 2020-10-01 13:34 ` finch.parker
2020-10-01 19:13 ` [ruby-core:100258] " grzegorz.jakubiak
` (15 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: finch.parker @ 2020-10-01 13:34 UTC (permalink / raw)
To: ruby-core
Issue #17200 has been updated by parker (Parker Finch).
* [#17016] Enumerable#scan_left (parker)
* This is a proposal to add a method to enumerable that accumulates the results of injecting an operation over the enumerable. There is interest in adding this method, but concern about the name. I think that `#accumulate` is a good name.
* Should we add this method?
* Is the name `#accumulate` acceptable?
----------------------------------------
Misc #17200: DevelopersMeeting20201026Japan
https://bugs.ruby-lang.org/issues/17200#change-87843
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2020/10/26 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/10/19 (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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:100258] [Ruby master Misc#17200] DevelopersMeeting20201026Japan
2020-09-28 23:24 [ruby-core:100206] [Ruby master Misc#17200] DevelopersMeeting20201026Japan mame
2020-10-01 13:34 ` [ruby-core:100256] " finch.parker
@ 2020-10-01 19:13 ` grzegorz.jakubiak
2020-10-01 19:41 ` [ruby-core:100260] " merch-redmine
` (14 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: grzegorz.jakubiak @ 2020-10-01 19:13 UTC (permalink / raw)
To: ruby-core
Issue #17200 has been updated by greggzst (Grzegorz Jakubiak).
* [Feature #16851] Ruby hashing algorithm could be improved using Tabulation Hashing
* Improves hashing algorithm
----------------------------------------
Misc #17200: DevelopersMeeting20201026Japan
https://bugs.ruby-lang.org/issues/17200#change-87846
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2020/10/26 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/10/19 (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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:100260] [Ruby master Misc#17200] DevelopersMeeting20201026Japan
2020-09-28 23:24 [ruby-core:100206] [Ruby master Misc#17200] DevelopersMeeting20201026Japan mame
2020-10-01 13:34 ` [ruby-core:100256] " finch.parker
2020-10-01 19:13 ` [ruby-core:100258] " grzegorz.jakubiak
@ 2020-10-01 19:41 ` merch-redmine
2020-10-01 22:58 ` [ruby-core:100268] " merch-redmine
` (13 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: merch-redmine @ 2020-10-01 19:41 UTC (permalink / raw)
To: ruby-core
Issue #17200 has been updated by jeremyevans0 (Jeremy Evans).
* [Bug #14012] NameError is raised when use class variables in Refinements (jeremyevans0)
* Refinement methods cannot reference class variables of the classes/modules they refine.
* Is this a bug or expected behavior?
* If a bug, how should class variable lookup work in refinement methods?
* [Bug #13768] SIGCHLD and Thread dead-lock problem (jeremyevans0)
* You can end up with thread deadlock even when a signal handler could result in breaking the deadlock.
* I don't think this is a bug, otherwise we would have to skip deadlock detection for all custom signal handlers.
* Do we want add a feature such as `Thread.ignore_deadlock = true` so that we can support this approach?
* [Bug #12485] Kernel.Rational raises TypeError though given denominator returns 1 by to_int (jeremyevans0)
* Do we want Kernel#Rational to fallback to checking for `to_int` if `to_r` is not defined?
* If so, is the patch acceptable?
* [Bug #11808] Different behavior between Enumerable#grep and Array#grep (jeremyevans0)
* Is the current behavior bug or expected?
* @nobu has a patch allowing regexp global variables to be available in blocks passed to Enumerable#grep.
* If current behavior is a bug, do we want to use @nobu's patch?
* [Bug #11202] No warning when a link to an original method body was removed (jeremyevans0)
* I don't think this is a bug. Do we want to add a warning in this case?
----------------------------------------
Misc #17200: DevelopersMeeting20201026Japan
https://bugs.ruby-lang.org/issues/17200#change-87847
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2020/10/26 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/10/19 (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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:100268] [Ruby master Misc#17200] DevelopersMeeting20201026Japan
2020-09-28 23:24 [ruby-core:100206] [Ruby master Misc#17200] DevelopersMeeting20201026Japan mame
` (2 preceding siblings ...)
2020-10-01 19:41 ` [ruby-core:100260] " merch-redmine
@ 2020-10-01 22:58 ` merch-redmine
2020-10-03 7:32 ` [ruby-core:100287] " glass.saga
` (12 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: merch-redmine @ 2020-10-01 22:58 UTC (permalink / raw)
To: ruby-core
Issue #17200 has been updated by jeremyevans0 (Jeremy Evans).
* [Feature #17143] Improve support for warning categories (jeremyevans0)
* Based on feedback at last month's developer meeting, I'm now proposing adding only two new categories: `:uninitialized_ivar` and `:redefine`.
* I have a pull request that adds support for those two categories and adds the `:deprecated` category to additional warnings, it is OK?
----------------------------------------
Misc #17200: DevelopersMeeting20201026Japan
https://bugs.ruby-lang.org/issues/17200#change-87855
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2020/10/26 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/10/19 (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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:100287] [Ruby master Misc#17200] DevelopersMeeting20201026Japan
2020-09-28 23:24 [ruby-core:100206] [Ruby master Misc#17200] DevelopersMeeting20201026Japan mame
` (3 preceding siblings ...)
2020-10-01 22:58 ` [ruby-core:100268] " merch-redmine
@ 2020-10-03 7:32 ` glass.saga
2020-10-06 9:39 ` [ruby-core:100307] " aycabta
` (11 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: glass.saga @ 2020-10-03 7:32 UTC (permalink / raw)
To: ruby-core
Issue #17200 has been updated by Glass_saga (Masaki Matsushita).
* [Feature #17187] Add connect_timeout to TCPSocket (glass)
* Could I merge it?
----------------------------------------
Misc #17200: DevelopersMeeting20201026Japan
https://bugs.ruby-lang.org/issues/17200#change-87872
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2020/10/26 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/10/19 (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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:100307] [Ruby master Misc#17200] DevelopersMeeting20201026Japan
2020-09-28 23:24 [ruby-core:100206] [Ruby master Misc#17200] DevelopersMeeting20201026Japan mame
` (4 preceding siblings ...)
2020-10-03 7:32 ` [ruby-core:100287] " glass.saga
@ 2020-10-06 9:39 ` aycabta
2020-10-11 12:06 ` [ruby-core:100372] " kazuki
` (10 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: aycabta @ 2020-10-06 9:39 UTC (permalink / raw)
To: ruby-core
Issue #17200 has been updated by aycabta (aycabta .).
* [Feature #16746] Endless method definition
* The following was discussed at [DevelopersMeeting20200514Japan](https://github.com/ruby/dev-meeting-log/blob/master/DevelopersMeeting20200514Japan.md)
> Conclusion:
>
> * matz: Let me have some time to consider this issue
> * `def foo() =` or `def foo() :`
> * `def foo(n) = n => @x`
> * `def foo=bar` may break compatibility (`def foo= bar; bar; end`); So, no-arugment mark `()` is mandatory. But I may reconsider
* [Feature #15921] R-assign (rightward-assignment) operator
* The following was discussed at [DevelopersMeeting20200514Japan](https://github.com/ruby/dev-meeting-log/blob/master/DevelopersMeeting20200514Japan.md)
> Conclusion:
>
> * matz: The motivation is still valid even after pipeline operator is gave up. It is still useful for a long method chain.
> * matz: I think an experiment with commit is needed and works. I will explain.
----------------------------------------
Misc #17200: DevelopersMeeting20201026Japan
https://bugs.ruby-lang.org/issues/17200#change-87892
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2020/10/26 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/10/19 (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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:100372] [Ruby master Misc#17200] DevelopersMeeting20201026Japan
2020-09-28 23:24 [ruby-core:100206] [Ruby master Misc#17200] DevelopersMeeting20201026Japan mame
` (5 preceding siblings ...)
2020-10-06 9:39 ` [ruby-core:100307] " aycabta
@ 2020-10-11 12:06 ` kazuki
2020-10-14 9:31 ` [ruby-core:100399] " eregontp
` (9 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: kazuki @ 2020-10-11 12:06 UTC (permalink / raw)
To: ruby-core
Issue #17200 has been updated by ktsj (Kazuki Tsujimoto).
* [Feature #17260] Promote pattern matching to official feature
* I'd like to remove single line pattern matching and experimental warnings.
----------------------------------------
Misc #17200: DevelopersMeeting20201026Japan
https://bugs.ruby-lang.org/issues/17200#change-87982
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2020/10/26 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/10/19 (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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:100399] [Ruby master Misc#17200] DevelopersMeeting20201026Japan
2020-09-28 23:24 [ruby-core:100206] [Ruby master Misc#17200] DevelopersMeeting20201026Japan mame
` (6 preceding siblings ...)
2020-10-11 12:06 ` [ruby-core:100372] " kazuki
@ 2020-10-14 9:31 ` eregontp
2020-10-16 5:39 ` [ruby-core:100417] " marcandre-ruby-core
` (8 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: eregontp @ 2020-10-14 9:31 UTC (permalink / raw)
To: ruby-core
Issue #17200 has been updated by Eregon (Benoit Daloze).
* [Feature #17259] Kernel#warn should ignore <internal: entries (eregon)
* Currently, `warn('message', uplevel: n)` can show `<internal:kernel>:90: warning: message` instead of `calling_file.rb:42: warning: message`.
* https://github.com/ruby/ruby/pull/3647 fixes it, OK to merge?
* Also, RubyGems redefines Kernel#warn for skipping RubyGems' require. That redefinition caused various incompatibilities. If we ignore `<internal:`, no need to redefine Kernel#warn (I'll make a PR to RubyGems).
----------------------------------------
Misc #17200: DevelopersMeeting20201026Japan
https://bugs.ruby-lang.org/issues/17200#change-88013
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2020/10/26 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/10/19 (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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:100417] [Ruby master Misc#17200] DevelopersMeeting20201026Japan
2020-09-28 23:24 [ruby-core:100206] [Ruby master Misc#17200] DevelopersMeeting20201026Japan mame
` (7 preceding siblings ...)
2020-10-14 9:31 ` [ruby-core:100399] " eregontp
@ 2020-10-16 5:39 ` marcandre-ruby-core
2020-10-18 0:36 ` [ruby-core:100421] " tenderlove
` (7 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: marcandre-ruby-core @ 2020-10-16 5:39 UTC (permalink / raw)
To: ruby-core
Issue #17200 has been updated by marcandre (Marc-Andre Lafortune).
* [Feature #17171] Have `private` affect constants and singleton methods definitions too (marcandre)
* Privacy is important for gems in particular. `private_constant` is verbose to use.
* The constants and methods affected would have special flag "legacy public"
* Ruby 3.0: warn (verbose only) on first access to "legacy public"
* Ruby 3.1: warn (always) on first access to "legacy public"
* Ruby 3.2: "legacy public" becomes private
----------------------------------------
Misc #17200: DevelopersMeeting20201026Japan
https://bugs.ruby-lang.org/issues/17200#change-88032
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2020/10/26 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/10/19 (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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:100421] [Ruby master Misc#17200] DevelopersMeeting20201026Japan
2020-09-28 23:24 [ruby-core:100206] [Ruby master Misc#17200] DevelopersMeeting20201026Japan mame
` (8 preceding siblings ...)
2020-10-16 5:39 ` [ruby-core:100417] " marcandre-ruby-core
@ 2020-10-18 0:36 ` tenderlove
2020-10-19 0:16 ` [ruby-core:100423] " marcandre-ruby-core
` (6 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: tenderlove @ 2020-10-18 0:36 UTC (permalink / raw)
To: ruby-core
Issue #17200 has been updated by tenderlovemaking (Aaron Patterson).
* [Feature #17176] GC.auto_compact / GC.auto_compact=(flag) (tenderlove)
* Currently compaction is a manual process, eventually I want to make it automatic
*. This feature lets users "opt in" to automatic compaction so we can test extensions
* Reference updating logic remains the same so "heap integrity" should be the same
----------------------------------------
Misc #17200: DevelopersMeeting20201026Japan
https://bugs.ruby-lang.org/issues/17200#change-88040
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2020/10/26 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/10/19 (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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:100423] [Ruby master Misc#17200] DevelopersMeeting20201026Japan
2020-09-28 23:24 [ruby-core:100206] [Ruby master Misc#17200] DevelopersMeeting20201026Japan mame
` (9 preceding siblings ...)
2020-10-18 0:36 ` [ruby-core:100421] " tenderlove
@ 2020-10-19 0:16 ` marcandre-ruby-core
2020-10-20 0:04 ` [ruby-core:100435] " hsbt
` (5 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: marcandre-ruby-core @ 2020-10-19 0:16 UTC (permalink / raw)
To: ruby-core
Issue #17200 has been updated by marcandre (Marc-Andre Lafortune).
* [Feature #17265] Have common ancestor `Bool` for `TrueClass` and `FalseClass` (marcandre)
* Useful for `RBS`
* Should have very limited incompatibility
----------------------------------------
Misc #17200: DevelopersMeeting20201026Japan
https://bugs.ruby-lang.org/issues/17200#change-88042
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2020/10/26 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/10/19 (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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:100435] [Ruby master Misc#17200] DevelopersMeeting20201026Japan
2020-09-28 23:24 [ruby-core:100206] [Ruby master Misc#17200] DevelopersMeeting20201026Japan mame
` (10 preceding siblings ...)
2020-10-19 0:16 ` [ruby-core:100423] " marcandre-ruby-core
@ 2020-10-20 0:04 ` hsbt
2020-10-21 16:37 ` [ruby-core:100475] " grzegorz.jakubiak
` (4 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: hsbt @ 2020-10-20 0:04 UTC (permalink / raw)
To: ruby-core
Issue #17200 has been updated by hsbt (Hiroshi SHIBATA).
* [Feature #17267] Remove Win32API at Ruby 3.0
* Does anyone oppose it?
----------------------------------------
Misc #17200: DevelopersMeeting20201026Japan
https://bugs.ruby-lang.org/issues/17200#change-88053
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2020/10/26 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/10/19 (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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:100475] [Ruby master Misc#17200] DevelopersMeeting20201026Japan
2020-09-28 23:24 [ruby-core:100206] [Ruby master Misc#17200] DevelopersMeeting20201026Japan mame
` (11 preceding siblings ...)
2020-10-20 0:04 ` [ruby-core:100435] " hsbt
@ 2020-10-21 16:37 ` grzegorz.jakubiak
2020-10-22 0:58 ` [ruby-core:100486] " ko1
` (3 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: grzegorz.jakubiak @ 2020-10-21 16:37 UTC (permalink / raw)
To: ruby-core
Issue #17200 has been updated by greggzst (Grzegorz Jakubiak).
* [Feature #17277] Make Enumerator#with_index yield row and col indices for Matrix
* Access Matrix indices in enumerable methods
----------------------------------------
Misc #17200: DevelopersMeeting20201026Japan
https://bugs.ruby-lang.org/issues/17200#change-88094
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2020/10/26 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/10/19 (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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:100486] [Ruby master Misc#17200] DevelopersMeeting20201026Japan
2020-09-28 23:24 [ruby-core:100206] [Ruby master Misc#17200] DevelopersMeeting20201026Japan mame
` (12 preceding siblings ...)
2020-10-21 16:37 ` [ruby-core:100475] " grzegorz.jakubiak
@ 2020-10-22 0:58 ` ko1
2020-10-22 17:17 ` [ruby-core:100508] " eregontp
` (2 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: ko1 @ 2020-10-22 0:58 UTC (permalink / raw)
To: ruby-core
Issue #17200 has been updated by ko1 (Koichi Sasada).
* [Bug #17146] Queue operations are allowed after it is frozen
* It is interesting question what "freeze" mean.
* [Feature #17256] Freeze all Regexp objects
* I feel it is too heavy to freeze all regexp...
* [Feature #17269] Frozen Process::Status
* low priority
* [Feature #17145] Ractor-aware `Object#deep_freeze`
* Can we define the meaning of class/module?
* [Feature #17270] ObjectSpace.each_object should be restricted on multi-Ractors
* already introduced, but need confirmation
* [Bug #17268] special global variables which can be accessed from ractors
* already introduced, but need confirmation
* [Feature #17261] Software transactional memory (STM) for Threads and Ractors
* Can I merge it with current naming and semantics?
* [Feature #17274] Ractor.make_shareable(obj)
* already introduced for convenience, but we can change.
* [Feature #17273] shareable_constant_value pragma
* is it acceptable?
----------------------------------------
Misc #17200: DevelopersMeeting20201026Japan
https://bugs.ruby-lang.org/issues/17200#change-88106
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2020/10/26 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/10/19 (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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:100508] [Ruby master Misc#17200] DevelopersMeeting20201026Japan
2020-09-28 23:24 [ruby-core:100206] [Ruby master Misc#17200] DevelopersMeeting20201026Japan mame
` (13 preceding siblings ...)
2020-10-22 0:58 ` [ruby-core:100486] " ko1
@ 2020-10-22 17:17 ` eregontp
2020-10-23 5:42 ` [ruby-core:100513] " nobu
2020-10-24 3:38 ` [ruby-core:100520] " koic.ito
16 siblings, 0 replies; 18+ messages in thread
From: eregontp @ 2020-10-22 17:17 UTC (permalink / raw)
To: ruby-core
Issue #17200 has been updated by Eregon (Benoit Daloze).
* [Bug #17280] Dir.glob with FNM_DOTMATCH matches ".." and "." and results in duplicated entries (eregon)
* What's the intended behavior?
----------------------------------------
Misc #17200: DevelopersMeeting20201026Japan
https://bugs.ruby-lang.org/issues/17200#change-88131
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2020/10/26 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/10/19 (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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:100513] [Ruby master Misc#17200] DevelopersMeeting20201026Japan
2020-09-28 23:24 [ruby-core:100206] [Ruby master Misc#17200] DevelopersMeeting20201026Japan mame
` (14 preceding siblings ...)
2020-10-22 17:17 ` [ruby-core:100508] " eregontp
@ 2020-10-23 5:42 ` nobu
2020-10-24 3:38 ` [ruby-core:100520] " koic.ito
16 siblings, 0 replies; 18+ messages in thread
From: nobu @ 2020-10-23 5:42 UTC (permalink / raw)
To: ruby-core
Issue #17200 has been updated by nobu (Nobuyoshi Nakada).
* [Feature #17281] Remove support for mathn
* mathn has been deprecated.
----------------------------------------
Misc #17200: DevelopersMeeting20201026Japan
https://bugs.ruby-lang.org/issues/17200#change-88135
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2020/10/26 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/10/19 (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/
^ permalink raw reply [flat|nested] 18+ messages in thread
* [ruby-core:100520] [Ruby master Misc#17200] DevelopersMeeting20201026Japan
2020-09-28 23:24 [ruby-core:100206] [Ruby master Misc#17200] DevelopersMeeting20201026Japan mame
` (15 preceding siblings ...)
2020-10-23 5:42 ` [ruby-core:100513] " nobu
@ 2020-10-24 3:38 ` koic.ito
16 siblings, 0 replies; 18+ messages in thread
From: koic.ito @ 2020-10-24 3:38 UTC (permalink / raw)
To: ruby-core
Issue #17200 has been updated by koic (Koichi ITO).
* [Ticket #17208] Add `Set#compact` and `Set#compact!` methods (koic)
* Is this proposal acceptable?
----------------------------------------
Misc #17200: DevelopersMeeting20201026Japan
https://bugs.ruby-lang.org/issues/17200#change-88143
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2020/10/26 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/10/19 (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/
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
^ permalink raw reply [flat|nested] 18+ messages in thread
end of thread, other threads:[~2020-10-24 3:38 UTC | newest]
Thread overview: 18+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-28 23:24 [ruby-core:100206] [Ruby master Misc#17200] DevelopersMeeting20201026Japan mame
2020-10-01 13:34 ` [ruby-core:100256] " finch.parker
2020-10-01 19:13 ` [ruby-core:100258] " grzegorz.jakubiak
2020-10-01 19:41 ` [ruby-core:100260] " merch-redmine
2020-10-01 22:58 ` [ruby-core:100268] " merch-redmine
2020-10-03 7:32 ` [ruby-core:100287] " glass.saga
2020-10-06 9:39 ` [ruby-core:100307] " aycabta
2020-10-11 12:06 ` [ruby-core:100372] " kazuki
2020-10-14 9:31 ` [ruby-core:100399] " eregontp
2020-10-16 5:39 ` [ruby-core:100417] " marcandre-ruby-core
2020-10-18 0:36 ` [ruby-core:100421] " tenderlove
2020-10-19 0:16 ` [ruby-core:100423] " marcandre-ruby-core
2020-10-20 0:04 ` [ruby-core:100435] " hsbt
2020-10-21 16:37 ` [ruby-core:100475] " grzegorz.jakubiak
2020-10-22 0:58 ` [ruby-core:100486] " ko1
2020-10-22 17:17 ` [ruby-core:100508] " eregontp
2020-10-23 5:42 ` [ruby-core:100513] " nobu
2020-10-24 3:38 ` [ruby-core:100520] " koic.ito
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).