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.0 required=3.0 tests=BAYES_00,DKIM_ADSP_NXDOMAIN, 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 68B481F4B5 for ; Thu, 14 Nov 2019 03:46:50 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 00F39120B4A; Thu, 14 Nov 2019 12:46:41 +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 7406D120B49 for ; Thu, 14 Nov 2019 12:46:38 +0900 (JST) Received: by filter0125p3las1.sendgrid.net with SMTP id filter0125p3las1-10052-5DCCCE20-2F 2019-11-14 03:46:40.93564203 +0000 UTC m=+508.344709584 Received: from herokuapp.com (unknown [54.173.123.162]) by ismtpd0113p1mdw1.sendgrid.net (SG) with ESMTP id CKUsqnSyQ5KDu3WpsxVkvg for ; Thu, 14 Nov 2019 03:46:40.610 +0000 (UTC) Date: Thu, 14 Nov 2019 03:46:40 +0000 (UTC) From: XrXr@users.noreply.github.com Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 71478 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 16262 X-Redmine-Issue-Author: mame X-Redmine-Sender: alanwu 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?PWg67P6owy8ojUUZg1G=2FQM4Z0jTQ2XLCqLM8Y2L8tUvRFuUPM6+aKANjRFY5CJ?= =?us-ascii?Q?rI4idck48+I9Qlj0f4ev6INVBzruzf1YJYe3DK+?= =?us-ascii?Q?g+ayvPtHimH2PLYJnAKbzPj4mBw+BMiXVwWVfJm?= =?us-ascii?Q?iGPKK5XACdepRHvljl7fEce1UGUop1TF=2FsgazG3?= =?us-ascii?Q?pJrLKiAW7wIB7ZLSvBsebWZJRNcsrj5RNkw=3D=3D?= To: ruby-core@ruby-lang.org X-ML-Name: ruby-core X-Mail-Count: 95848 Subject: [ruby-core:95848] [Ruby master Misc#16262] DevelopersMeeting20191128Japan 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 #16262 has been updated by alanwu (Alan Wu). - [Bug #15620] Block argument usage affects lambda semantic - I find the current behaviour unreasonably confusing and would like to see improvement, even though the bug doesn't really show up in the real world often. - I have a [pull request](https://github.com/ruby/ruby/pull/2289) which restores the behaviour found in Ruby 2.4.x and warns about it, based off of matz's comment in [[ruby-core:94054]](http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/94054). - Could someone confirm that is the desired fix? If it is the fix we want, could someone review the PR? ---------------------------------------- Misc #16262: DevelopersMeeting20191128Japan https://bugs.ruby-lang.org/issues/16262#change-82681 * 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/11/28 13:00-17:00 Place, Sign-up, and Log: https://docs.google.com/document/d/1AZ74HXEedKksJwhEUPIlnRxAUgchndZPZYAKjGPMsFI/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/