archive (unofficial mirror)
 help / color / Atom feed
Subject: [ruby-core:95777] [Ruby master Misc#16262] DevelopersMeeting20191128Japan
Date: Sun, 10 Nov 2019 14:00:51 +0000 (UTC)
Message-ID: <> (raw)
In-Reply-To: <>

Issue #16262 has been updated by methodmissing (Lourens Naudé).

* [Misc #16291] Introduce support for resize in rb_ary_freeze and prefer internal use of rb_ary_freeze and rb_str_freeze for String and Array types (lourens)
  - 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_freeze` 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 capability to user code too (as recommended by Shyouhei) for parity with `String#freeze` already doing the same

Misc #16262: DevelopersMeeting20191128Japan

* 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:


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


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


Unsubscribe: <>

  parent reply index

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2019-10-18 12:03 ` [ruby-core:95420] " mame
2019-10-18 12:08 ` [ruby-core:95421] " mame
2019-10-18 16:12 ` [ruby-core:95423] " merch-redmine
2019-10-22 22:58 ` [ruby-core:95484] " duerst
2019-10-26 12:42 ` [ruby-core:95564] " zverok.offline
2019-11-04 21:13 ` [ruby-core:95678] " jonathan
2019-11-05 12:20 ` [ruby-core:95697] " manga.osyo
2019-11-10 14:00 ` lourens [this message]
2019-11-14  3:46 ` [ruby-core:95848] " XrXr
2019-11-24  2:25 ` [ruby-core:95919] " mame
2019-11-24  3:14 ` [ruby-core:95921] " mail
2019-11-24  9:19 ` [ruby-core:95922] " kazuki
2019-11-24 22:46 ` [ruby-core:95929] " eregontp
2019-11-24 23:14 ` [ruby-core:95932] " mame
2019-11-25  6:00 ` [ruby-core:95938] " sawadatsuyoshi
2019-11-27  1:06 ` [ruby-core:95969] " lourens
2019-11-27 11:58 ` [ruby-core:95979] " hsbt
2019-11-27 12:49 ` [ruby-core:95980] " zverok.offline
2019-11-28  6:40 ` [ruby-core:96013] " jean.boussier
2019-11-28 10:15 ` [ruby-core:96019] " eregontp
2019-11-30  4:06 ` [ruby-core:96033] " mame

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link archive (unofficial mirror)

Archives are clonable: git clone --mirror

Example config snippet for mirrors

Newsgroups are available over NNTP:

 note: .onion URLs require Tor:

AGPL code for this site: git clone