< :前の番号
^ :番号順リスト
> :次の番号
P :前の記事（スレッド移動）
N :次の記事（スレッド移動）
|<:前のスレッド
>|:次のスレッド
^ :返事先
_:自分への返事
>:同じ返事先を持つ記事（前）
<:同じ返事先を持つ記事（後）
---:分割してスレッド表示、再表示
| :分割して（縦）スレッド表示、再表示
~ :スレッドのフレーム消去
.:インデックス
..:インデックスのインデックス
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: <mailto:ruby-core-request / ruby-lang.org?subject=3Dunsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>