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


* [Bug #15928] Constant declaration does not conform to JIS 3017:2013 (jeremyevans0)
  * Do we want to make constant assignment evaluation similar to attribute assignment (e.g. use left-to-right evaluation)?
  * We recently made a similar change to make multiple assignment use left-to-right evaluation (#4443), and I think constant assignment should operate the same way.
* [Bug #17767] `Cloned ENV` inconsistently returns `ENV` or `self` (jeremyevans0)
  * How should `ENV.dup` and `ENV.clone` work?
  * I propose to have them return `ENV`, since they share the same storage.
  * If we do want `ENV.dup` and `ENV.clone` to return `ENV`, is the patch acceptable?
* [Bug #13876] Tempfile's finalizer can be interrupted by a Timeout exception which can cause the process to hang (jeremyevans0)
  * Currently, exceptions can be raised during finalizer processing (in GC context), causing process hangs.
  * Can we mark when a thread is running finalizers and not check for pending interrupts in that case, as the patch does?
* [Bug #17739] Array#sort! changes the order even if the receiver raises FrozenError in given block (jeremyevans0)
  * Currently, freezing an array inside Array#sort! allows further changes to the array.
  * Should we prevent further changes to the array by checking whether the array is frozen each time the block returns?
* [Bug #17631] `Numeric#real?` incorrectly returns true for `NaN` and `INFINITY` (jeremyevans0)
  * Is the current behavior of `real?` and `complex?` expected, where `Complex#real?` is always `false` and `Numeric#real?` is always `true`?
  * I believe so and think this bug should be closed, but I would like to get confirmation.

----------------------------------------
Misc #17811: DevelopersMeeting20210521Japan
https://bugs.ruby-lang.org/issues/17811#change-91890

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

**Date: 2021/05/21 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.
```

- It is recommended to add a comment by 2021/05/18. We hold a preparatory meeting to create an agenda a few days before the dev-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. We appreciate it if you could write a short summary and update from a previous discussion.




-- 
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>