From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-3.9 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id 536F71F461 for ; Mon, 26 Aug 2019 22:12:08 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id A56A0120BA8; Tue, 27 Aug 2019 07:11:48 +0900 (JST) Received: from o1678948x4.outbound-mail.sendgrid.net (o1678948x4.outbound-mail.sendgrid.net [167.89.48.4]) by neon.ruby-lang.org (Postfix) with ESMTPS id 937B1120B86 for ; Tue, 27 Aug 2019 07:11:46 +0900 (JST) Received: by filter0035p3iad2.sendgrid.net with SMTP id filter0035p3iad2-31346-5D645922-33 2019-08-26 22:11:46.845437413 +0000 UTC m=+941342.420570550 Received: from herokuapp.com (unknown [54.242.199.255]) by ismtpd0068p1mdw1.sendgrid.net (SG) with ESMTP id S2lW6eVTR12HuawHb9mLQg for ; Mon, 26 Aug 2019 22:11:46.737 +0000 (UTC) Date: Mon, 26 Aug 2019 22:11:46 +0000 (UTC) From: daniel@dan42.com Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 70142 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 15996 X-Redmine-Issue-Author: mame X-Redmine-Sender: Dan0042 X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-SG-EID: =?us-ascii?Q?8sy4RigFvRTdBfCVJrT9zb2J88PC92TMQwdNgaWYaq6BHBXJTWxxaDSxpjQPw7?= =?us-ascii?Q?+MPihppTzQ1vPsd2sruuVpfqfFdgkoWYvoMRBCk?= =?us-ascii?Q?=2FF2+mFIuGa3QJ2K2S7sV=2FAttOUOOvQvVD0zn4RZ?= =?us-ascii?Q?zLHtR6CP=2FJgZSezYapemDEW6reVYS8UMKBxG3yP?= =?us-ascii?Q?fI=2Fh5USWjIMOB1010hf9F0v5nIXHi3ehypw=3D=3D?= To: ruby-core@ruby-lang.org X-ML-Name: ruby-core X-Mail-Count: 94590 Subject: [ruby-core:94590] [Ruby master Misc#15996] DevelopersMeeting20190829Japan X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #15996 has been updated by Dan0042 (Daniel DeLorme). * [Feature #10829] Add to_proc method to the Array class * [Feature #12115] Add Symbol#call to allow to_proc shorthand with arguments * [Feature #15302] Proc#with and Proc#by, for partial function application and currying * [Misc #15723] Reconsider numbered parameters * [Feature #15897] `it` as a default block parameter * [Feature #16113] Partial application * [Feature #16120] Implicit block argument if block starts with dot-method call * All proposals above are different ideas for a block shorthand more versatile than `(&:to_s)` * Insatisfaction with numbered parameters solution * In #16120 I try to analyze the root issue common to all the above ---------------------------------------- Misc #15996: DevelopersMeeting20190829Japan https://bugs.ruby-lang.org/issues/15996#change-81062 * 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/08/29 (Thu) Time: 13:00-17:00 (JST) Place and Sign-up: https://connpass.com/event/139231/ log: https://docs.google.com/document/d/1XypDO1crRV9uNg1_ajxkljVdN8Vdyl5hnz462bDQw34/edit # 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/