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 2D1461F454 for ; Sun, 10 Nov 2019 14:01:03 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 5D0BA1209A5; Sun, 10 Nov 2019 23:00:52 +0900 (JST) Received: from xtrwkhkc.outbound-mail.sendgrid.net (xtrwkhkc.outbound-mail.sendgrid.net [167.89.16.28]) by neon.ruby-lang.org (Postfix) with ESMTPS id 9F7651209A4 for ; Sun, 10 Nov 2019 23:00:48 +0900 (JST) Received: by filter0168p3mdw1.sendgrid.net with SMTP id filter0168p3mdw1-14728-5DC81813-34 2019-11-10 14:00:51.425926475 +0000 UTC m=+232827.653816665 Received: from herokuapp.com (unknown [3.92.225.197]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id DsJbPjEeTPSzaMO9mGz1RQ for ; Sun, 10 Nov 2019 14:00:51.317 +0000 (UTC) Date: Sun, 10 Nov 2019 14:00:51 +0000 (UTC) From: lourens@bearmetal.eu Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 71402 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 16262 X-Redmine-Issue-Author: mame X-Redmine-Sender: methodmissing 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?Fr=2F4MkNsnJ5O85XS4movydqTd1a9M98=2FgJAFvUl026Ph=2F+AIHO3I3HbiSjfp=2Fp?= =?us-ascii?Q?uriFK93okdUpm0Aame1A0ZkmRgt+wYCrcw68RNU?= =?us-ascii?Q?NTBcDgJdC67L=2F1ob+MuwzuO0xZwWMj5oKWYIMpq?= =?us-ascii?Q?k7XFtaHykaySCUgvflf4MKlPIrAOsZw4gW3ldjg?= =?us-ascii?Q?9NnTXTo8QCbUEw=2FWQo1W9vi8Fg7gf0XuwHA=3D=3D?= To: ruby-core@ruby-lang.org X-ML-Name: ruby-core X-Mail-Count: 95777 Subject: [ruby-core:95777] [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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #16262 has been updated by methodmissing (Lourens Naud=E9). * [Misc #16291] Introduce support for resize in rb_ary_freeze and prefer in= ternal use of rb_ary_freeze and rb_str_freeze for String and Array types (l= ourens) - Builds onto the capacity shrinking feature introduced by `rb_str_freeze= `, targeting `Array` - Many internal uses that froze `String` types did not use the `rb_str_fr= eeze` variation and could not benefit from resizing capacity on freeze - Implemented the same for `Array` - Let `Array#freeze` call `rb_ary_freeze` to expose the shrinking capabil= ity to user code too (as recommended by Shyouhei) for parity with `String#f= reeze` already doing the same ---------------------------------------- Misc #16262: DevelopersMeeting20191128Japan https://bugs.ruby-lang.org/issues/16262#change-82601 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal * Assignee: = ---------------------------------------- Please comment on your favorite ticket numbers you want to ask to discuss w= ith 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/1AZ74HXEedKksJw= hEUPIlnRxAUgchndZPZYAKjGPMsFI/edit# # NOTES - Dev meeting *IS NOT* a decision-making place. All decisions should be don= e 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 unders= tand your issue). - We will write a log about the discussion to a file or to each ticket in E= nglish. - All activities are best-effort (keep in mind that most of us are voluntee= r developers). - The date, time and place are scheduled according to when/where we can res= erve 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 followi= ng 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 as= k 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 discus= s 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 d= iscussion 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: