[ruby-core:96492] [Ruby master Misc#16454] DevelopersMeeting20200116Japan

[mame@ruby-lang.org]

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


Carry-over:

* [Bug #8841] Module#included_modules and prepended modules (mame)
  * Module#include? and Module#included_modules regard prepended modules as included (not well documented); Module#included is not called when the module is prepended. Is this right?
  * IMO, changing the behavior is no longer acceptable (without any actual trouble). How about just changing the document?

* [Feature #8026] Need Module#prepended_modules (mame)
  * It is accepted six years ago, but not implemented yet. I've never heard any actual trouble, but should we still add the feature?

* [Bug #9815] attr_reader doesn't warn on a uninitialized instance variable (mame)
  * A reader method defined by attr_reader :foo is not warned as "instance variable @foo not initialized". Is it intentional?

* [Bug #10388] Operator precedence problem in multiple assignment (massign) (mame)
  * "`a, b = c = 1, 2` is currently taken as `a, b = (c = 1), 2`; I'd expect it to be taken as `a, b = (c = 1, 2)`." Jeremy gave a try to implement but seemed difficult due to the limitation of LALR(1) parser. Let's give up.

* [Bug #10475] Array#flatten should not accept a nil argument (mame)
  * Should we add a document that Array#flatten accepts nil? Negative argument too?

* [Bug #10929] NilClass#to_proc and & don't mix? (mame)
  * I think it is not worth adding.

* [Bug #11014] String#partition doesn't return correct result on zero-width match (mame)
  * I'd like to confirm if the current behavior is inteneded.

* [Feature #16432] Using _1 inside binding.irb will cause unintended behavior (osyo)
  * Calling binding.irb in a block that uses _1 and using _1 in irb will cause unintended behavior.
  * Should it be a runtime error?

----------------------------------------
Misc #16454: DevelopersMeeting20200116Japan
https://bugs.ruby-lang.org/issues/16454#change-83422

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

**Date: 2020/01/16 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/01/09 (one week ago)
- 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/