[ruby-core:96093] [Ruby master Misc#16393] DevelopersMeeting20191220Japan

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


* [Feature #14183] "Real" keyword argument (jeremyevans0)
  * Is it OK to merge branch to remove deprecated support for positional hash <-> keyword conversion after 2.7 released?
* [Bug #11022] opening an eigenclass does not change the class variable definition context (jeremyevans0)
  * Discussed during September dev meeting, matz wanted to consider for a while. Has a decision been made?
* [Bug #7844] include/prepend satisfiable module dependencies are not satisfied (jeremyevans0)
  * Discussed during September dev meeting, matz wanted to consider for a while. Has a decision been made?
* [Bug #14240] warn four special variables: $; $, $/ $\ (jeremyevans0)
  * Do we still want to warn regarding these variables? If so, should the warnings be during parsing or at runtime (if variables are aliased and then modified)?
* [Feature #10463] :~@ and :!@ are not parsed correctly (jeremyevans0)
  * matz decided in July that `def ~@` and `def !@` should continue to work. However, can we fix the parser to not treat `:~@` and `:!@` as `:~` and `:!`?

----------------------------------------
Misc #16393: DevelopersMeeting20191220Japan
https://bugs.ruby-lang.org/issues/16393#change-82951

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment on your favorite ticket numbers you want to ask to discuss with your *SHORT* comment or summary.
(your summary/comment will help us because we don't need to read all of the ticket comments)

*DO NOT* discuss then on this ticket, please.

----
Date: 2019/12/20 13:00-17:00
Place, Sign-up, and Log: https://docs.google.com/document/d/18v0UWXwwKaSvOFp1UQbEnt_4p0BMTdoGgcNfjyAWTKs

# NOTES

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

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Discussion

----

Please comment on your favorite ticket we need to discuss with *the following format*.

```
* [Ticket ref] Ticket title (your name)
  * your comment why you want to put this ticket here if you want to add.
```

Your comment is very important if you are no attendee because we can not ask why you want to discuss it.

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

**Please follow the comment format strictly!**  We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86).  We may ignore a comment that violates the format.

**A short summary of a ticket is strongly recommended. We cannot read all discussion of the ticket in a limited time.**
A proposal is often changed during the discussion, so it is very helpful to summarize the latest/current proposal, post it as a comment in the ticket, and write a link to the comment. 




-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>