[ruby-core:108787] [Ruby master Misc#18803] DevMeeting-2022-06-16

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


* [Feature #18788] Support passing Regexp options as String to Regexp.new (jeremyevans0)
  * Do we want to add support for `Regexp.new(code, options)`, where options is a string (e.g. 'im').
  * @nobu pointed out it is already possible to get identical behavior using `Regexp.new("(?#{options}:#{code})")`.
* [Feature #18749] Strangeness of endless inclusive ranges (jeremyevans0)
  * Currently, we support both endless inclusive ranges and endless exclusive ranges.
  * Endless exclusive ranges do not contain endless inclusive ranges.
  * Do we want to convert endless inclusive ranges to endless exclusive ranges?
  * Do we want to keep supporting both, but consider them equal?
* [Feature #18461] closures are capturing unused variables (jeremyevans0)
  * Should procs capture local variables they do not use syntactically inside the proc?
  * Currently, they do, which I believe is expected and desired.
  * Removing this ability would remove the ability to using eval inside the proc to get access to the local variable.
  * Changing the behavior could allow for earlier garbage collection, and potentially improve performance.
* [Feature #18279] ENV.merge! support multiple arguments as Hash.merge! (jeremyevans0)
  * Can we add this ability?
  * @nobu has already prepared a patch.

----------------------------------------
Misc #18803: DevMeeting-2022-06-16
https://bugs.ruby-lang.org/issues/18803#change-97854

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

**Date: 2022/06/16 13:00-17:00** (JST)
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 record of the discussion in the 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 of the meeting 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 2022/06/13. 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:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>