[ruby-core:99257] [Ruby master Misc#17041] DevelopersMeeting20200826Japan

[ruby-core:99257] [Ruby master Misc#17041] DevelopersMeeting20200826Japan

[mame]

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

----------------------------------------
Misc #17041: DevelopersMeeting20200826Japan
https://bugs.ruby-lang.org/issues/17041

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

**Date: 2020/08/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/08/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/

[ruby-core:99258] [Ruby master Misc#17041] DevelopersMeeting20200826Japan

[zn]

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


* [Feature #17039] Remove `Time#succ` (znz)
  * `Time#succ` is obsolete since 1.9.2.

----------------------------------------
Misc #17041: DevelopersMeeting20200826Japan
https://bugs.ruby-lang.org/issues/17041#change-86642

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

**Date: 2020/08/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/08/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/

[ruby-core:99259] [Ruby master Misc#17041] DevelopersMeeting20200826Japan

[shyouhei]

Issue #17041 has been updated by shyouhei (Shyouhei Urabe).


- [Feature #17040] cleanup include/ruby/backward* (shyouhei)
    - Is anybody against it?

----------------------------------------
Misc #17041: DevelopersMeeting20200826Japan
https://bugs.ruby-lang.org/issues/17041#change-86643

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

**Date: 2020/08/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/08/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/

[ruby-core:99261] [Ruby master Misc#17041] DevelopersMeeting20200826Japan

[mame]

Issue #17041 has been updated by mame (Yusuke Endoh).


Please note that it may not be possible to go though all topics that are raised in this agenda because we will discuss 2.8/3.0 release schedule.  (Perhaps, we will prioritize the topics related to 2.8/3.0, such as Ractor.)  Thanks.

----------------------------------------
Misc #17041: DevelopersMeeting20200826Japan
https://bugs.ruby-lang.org/issues/17041#change-86645

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

**Date: 2020/08/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/08/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/

[ruby-core:99271] [Ruby master Misc#17041] DevelopersMeeting20200826Japan

[marcandre-ruby-core]

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


* [Feature #16989] Sets need ♥️, aka the "Set Program" (marcandre)
  * Bring `Set` into core
  * Insure interoperability with `Array` (e.g so `array & set` works and is efficient)
  * Shorthand syntax for static frozen sets of string/symbols (e.g. `%ws{hello world}`)

----------------------------------------
Misc #17041: DevelopersMeeting20200826Japan
https://bugs.ruby-lang.org/issues/17041#change-86658

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

**Date: 2020/08/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/08/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/

[ruby-core:99376] [Ruby master Misc#17041] DevelopersMeeting20200826Japan

[merch-redmine]

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


* [Feature #17055] Allow suppressing uninitialized instance variable and method redefined verbose mode warnings (jeremyevans0)
  * This keeps the default behavior the same as before, but allows opt-in to supress the warnings.
  * This allows for high-performance code (uninitialized instance variables) and safe code (redefining methods without removing in multi-thread environments) to work without issuing warnings in verbose mode.
  * Is it OK to commit the patch?

----------------------------------------
Misc #17041: DevelopersMeeting20200826Japan
https://bugs.ruby-lang.org/issues/17041#change-86781

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

**Date: 2020/08/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/08/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/

[ruby-core:99437] [Ruby master Misc#17041] DevelopersMeeting20200826Japan

[eregontp]

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


* [Feature #14844] Future of RubyVM::AST? (eregon)
  * Other Ruby implementations need to be able to implement it too given more and more gems use it. Where do we move it?
* [Feature #15752] A dedicated module for experimental features (eregon)
  * Create `ExperimentalFeatures` and move things there or `RubyVM` exists on all Ruby implementations? Please choose.

----------------------------------------
Misc #17041: DevelopersMeeting20200826Japan
https://bugs.ruby-lang.org/issues/17041#change-86892

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

**Date: 2020/08/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/08/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/

[ruby-core:99455] [Ruby master Misc#17041] DevelopersMeeting20200826Japan

[daniel]

Issue #17041 has been updated by Dan0042 (Daniel DeLorme).


* [Bug #17017] Range#max & Range#minmax incorrectly use Float end as max (dan0042)
  * `(1..3.1).max` has resulted in `3.1` since ruby 1.9 and has now been "fixed" to return `3`. Matz, please confirm?

----------------------------------------
Misc #17041: DevelopersMeeting20200826Japan
https://bugs.ruby-lang.org/issues/17041#change-86912

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

**Date: 2020/08/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/08/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/

[ruby-core:99475] [Ruby master Misc#17041] DevelopersMeeting20200826Japan

[jean.boussier]

Issue #17041 has been updated by byroot (Jean Boussier).


* [Bug #17020] `ObjectSpace.trace_object_allocations_stop` raises if called before `trace_object_allocations_start` (byroot)
  * It's a minor bug, but requires some annoying workarounds.
* [Feature #17103] Add a :since option to `ObjectSpace.dump_all` (byroot)
  * On large heap, `dump_all` can take over a minute and generate huge (6+GiB) files.
  * Sometimes you are only interested in objects allocated past a certain point, this make that use case much faster and efficient.


----------------------------------------
Misc #17041: DevelopersMeeting20200826Japan
https://bugs.ruby-lang.org/issues/17041#change-86930

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

**Date: 2020/08/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/08/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/

[ruby-core:99498] [Ruby master Misc#17041] DevelopersMeeting20200826Japan

[eregontp]

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


* [Feature #17104] Do not freeze interpolated strings when using frozen-string-literal (eregon)
  * It seems many people agree there is no point to freeze interpolated strings.
  * Interpolated strings are not "simple literals" (just like `1 + 2` is not a literal) and they involve mutation anyway, it seems of very little value to freeze, and it's inconvenient.

----------------------------------------
Misc #17041: DevelopersMeeting20200826Japan
https://bugs.ruby-lang.org/issues/17041#change-86956

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

**Date: 2020/08/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/08/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/

[ruby-core:99521] [Ruby master Misc#17041] DevelopersMeeting20200826Japan

[jean.boussier]

Issue #17041 has been updated by byroot (Jean Boussier).


* [Feature #13381] Expose rb_fstring and its family to C extensions
  * It's only missing a decision on the names. Could this be discussed again?

----------------------------------------
Misc #17041: DevelopersMeeting20200826Japan
https://bugs.ruby-lang.org/issues/17041#change-86982

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

**Date: 2020/08/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/08/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/

[ruby-core:99525] [Ruby master Misc#17041] DevelopersMeeting20200826Japan

[eregontp]

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


* [Bug #17105] A single `return` can return to two different places in a proc inside a lambda inside a method (eregon)
  * Is current implementation correct? Should it not be a `LocalJumpError` if the surrounding lambda is no longer on stack?

----------------------------------------
Misc #17041: DevelopersMeeting20200826Japan
https://bugs.ruby-lang.org/issues/17041#change-86985

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

**Date: 2020/08/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/08/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/

[ruby-core:99637] [Ruby master Misc#17041] DevelopersMeeting20200826Japan

[zn]

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



* [Feature #17125] Remove `Thread.exclusive` (znz)
  * `Thread.exclusive` is deprecated since 2.3.

----------------------------------------
Misc #17041: DevelopersMeeting20200826Japan
https://bugs.ruby-lang.org/issues/17041#change-87117

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

**Date: 2020/08/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/08/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/

[ruby-core:99644] [Ruby master Misc#17041] DevelopersMeeting20200826Japan

[mame]

Issue #17041 has been updated by mame (Yusuke Endoh).


* [Feature #17122] Add category to Warning#warn (mame)
  * I'd like to hear opinions from the committers

----------------------------------------
Misc #17041: DevelopersMeeting20200826Japan
https://bugs.ruby-lang.org/issues/17041#change-87125

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

**Date: 2020/08/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/08/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/

[ruby-core:99691] [Ruby master Misc#17041] DevelopersMeeting20200826Japan

[muraken]

Issue #17041 has been updated by mrkn (Kenta Murata).


- [[Feature #14723]](https://bugs.ruby-lang.org/issues/14722) python's buffer protocol clone (mrkn)
    - I renamed `buffer` to `memory_view`.
        - This name is already used in Python for the Python object wrapper of `PyBuffer`.
    - I've added tests for some functions and a simple memory view implementation of a String for testing these functions.
        - https://github.com/ruby/ruby/pull/3261/files

----------------------------------------
Misc #17041: DevelopersMeeting20200826Japan
https://bugs.ruby-lang.org/issues/17041#change-87182

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

**Date: 2020/08/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/08/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/

[ruby-core:99693] [Ruby master Misc#17041] DevelopersMeeting20200826Japan

[muraken]

Issue #17041 has been updated by mrkn (Kenta Murata).


* [[Feature #16812]](https://bugs.ruby-lang.org/issues/16812) Allow slicing arrays with ArithmeticSequence (mrkn)

  * I found the wrong test case, so the implementation was also in wrong state.  The proposed patch has been fixed.
  * There are opposing opinions in the following case:

    ```ruby
    [0,1,2,3,4,5][(6..0)%-2] #=> [5, 3, 1]

    # or

    [0,1,2,3,4,5][(6..0)%-2] #=> [4, 2, 0]
    ```

  * Python follows the former.

    ```py
    >>> [0, 1, 2, 3, 4, 5][6::-2]
    [5, 3, 1]
    ```

----------------------------------------
Misc #17041: DevelopersMeeting20200826Japan
https://bugs.ruby-lang.org/issues/17041#change-87184

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

**Date: 2020/08/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/08/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/

[ruby-core:99704] [Ruby master Misc#17041] DevelopersMeeting20200826Japan

[mame]

Issue #17041 has been updated by mame (Yusuke Endoh).


The meeting was postponed to the next Monday (31th Aug.) for some reason.

----------------------------------------
Misc #17041: DevelopersMeeting20200826Japan
https://bugs.ruby-lang.org/issues/17041#change-87194

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

**Date: 2020/08/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/08/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/

[ruby-core:99727] [Ruby master Misc#17041] DevelopersMeeting20200831Japan

[duerst]

Issue #17041 has been updated by duerst (Martin Dürst).

Subject changed from DevelopersMeeting20200826Japan to DevelopersMeeting20200831Japan

Adjust subject to match new date.

----------------------------------------
Misc #17041: DevelopersMeeting20200831Japan
https://bugs.ruby-lang.org/issues/17041#change-87220

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

**Date: 2020/08/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/08/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>