Misc #15930
closed
DevelopersMeeting20190711Japan
Added by mame (Yusuke Endoh) about 5 years ago.
Updated about 5 years ago.
Description
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/07/11 (Thu)
Time: 13:00-17:00 (JST)
Place and Sign-up: https://ruby.connpass.com/event/135823/
log: https://docs.google.com/document/d/1K61SGIwp8_rNsPyhmayUcERu71vt_etDjXdhqrLmBVY/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 agenda if the comment violate the format (because it is hard to copy&paste).
Related issues
1 (1 open — 0 closed)
- Description updated (diff)
- Description updated (diff)
- [Feature #5400] Remove flip-flops in 2.0
- [Feature #15950]Allow negative length in
Array#[]
, Array#[]=
, Array#slice
, Array#slice!
, String#[]
, String#[]=
, String#slice
, String#slice!
- 長さの負の値を許し、その場合に左向きに長さを測る提案です。
- 文字列の右端の定められた長さを取り出すときなどに便利だと思います。
- これにより、これまで存在していた左端との非対称性を解消できます。
- これまで
nil
を返していた一部の場合で文字列を返すようになります。
[Feature #15958] Time#inspect with frac
- [Feature #14385] Deprecate back-tick for Ruby 3.
- What does matz want to use backticks for?
- It seems too incompatible of a change, isn't it?
- [Bug #15708] Implicit numbered argument decomposes an array
- What's the reason of current behavior? Please explain on the ticket.
- matz: Can you judge whether that behavior is worth the inconsistency with
{ |x|
and making #map, etc not work with unknown element types (if elements can or not be arrays)?
- [Feature #15966] Introducing experimental features behind a flag, disabled by default
- Could you read the description and reply what you think? Do you think it's a good idea? I think it would be a much better way to introduce experimental features.
- [Feature #15973] Make
Kernel#lambda
always return lambda
- [Feature #11460] Unhelpful error message when naming a module with the same name as an existing class
- [Feature #15631] Let round_capa for ID table not allocate excess capacity for power of 2 ints >= 4
- [Feature #15987] Let boolean option (such as
exception
in Kernel#Complex
, Kernel#Float
, Kernel#Integer
, Kernel#Rational
) be falsy vs. truthy
- Does this issue need matz approval or can it be fixed directly? If it does, does matz agree we should address this and use RTEST()?
- [Feature #15865]
<expr> in <pattern>
expression (mame)
- We have some opinions: scoping, matching strictness, the keyword
in
, and the word order. But all are not specific to the one-line matching. I think it is acceptable if case/in
matching is acceptable. May I experimentally commit it as well as case/in
?
- [Bug #10463] :~@ and :!@ are not parsed correctly (jeremyevans0)
- Can we deprecate the automatic conversion of
~@
to ~
and !@
to !
in method names and symbols?
- [Misc #15805] Let memory sizes of the various IMEMO object types be reflected correctly
- [Misc #15806] Explicitly initialise encodings on init to remove branches on encoding lookup
- Currently
rb_enc_from_index
and related methods explicitly check for encoding table init on each call - I think this should be initialised at boot time instead as even the simple case of loading the interpreter requires the encoding table to be loaded anyways (symbol.c
)
- PR: https://github.com/ruby/ruby/pull/2128
- Status changed from Open to Closed
Also available in: Atom
PDF
Like0
Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0