[ruby-core:94959] [Ruby master Misc#16152] DevelopersMeeting20190919Japan

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


* [Feature #16120] Omitted block argument if block starts with dot-method call
   * `posts.map{ .author.name }` has *beautiful* readability, no incompatibility, changes a syntax error into an intuitive idiom, already implemented in 6 lines by nobu. 本当に美しいと思います。
* [Feature #16153] eventually_frozen flag to gradually phase-in frozen strings
   * This would make previous backward-incompatible proposals (#16150, #15836, #11473) possible with a backward-compatible transition.
* [Feature #16021] floor/ceil/round/truncate should accept a :step argument
   * Since Time#floor/ceil methods were added, it would be convenient to round to the previous/next minute/hour: `Time.now.ceil(step:60)`. Also add to Numeric, for convenience and consistency.
   * If this is a good idea I would like to try writing it.


----------------------------------------
Misc #16152: DevelopersMeeting20190919Japan
https://bugs.ruby-lang.org/issues/16152#change-81578

* 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/09/19 (Thu)
Time: 13:00-17:00 (JST)
Place: (Written in the Log)
Sign-up: (Add your name in the Log) 
Log: https://docs.google.com/document/d/1oYWVhH6BEgTNy8PxMUd-MS3JUK0kQMw43q5saBp8aZk

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

We don't guarantee to put tickets in the agenda if the comment violates the format (because it is hard to copy&paste).

**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:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>