Misc #17041
closedDevelopersMeeting20200831Japan
Description
The next dev meeting¶
Date: 2020/08/26 13:00-17:00
Place/Sign-up/Agenda/Log: https://github.com/ruby/dev-meeting-log/blob/master/DevelopersMeeting20200826Japan.md
- 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.
- DO NOT discuss then on this ticket, please.
Call for agenda items¶
If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:
* [Ticket ref] Ticket title (your name)
* Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)
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.
- Comment deadline: 2020/08/19 (one week before the meeting)
- The format is strict. We'll use this script to automatically create an markdown-style agenda. We may ignore a comment that does not follow the format.
- Your comment is mandatory. We cannot read all discussion of the ticket in a limited time.
Updated by mame (Yusuke Endoh) over 4 years ago
- Related to Misc #14770: [META] DevelopersMeeting added
Updated by znz (Kazuhiro NISHIYAMA) over 4 years ago
- [Feature #17039] Remove
Time#succ
(znz)-
Time#succ
is obsolete since 1.9.2.
-
Updated by shyouhei (Shyouhei Urabe) over 4 years ago
- [Feature #17040] cleanup include/ruby/backward* (shyouhei)
- Is anybody against it?
Updated by mame (Yusuke Endoh) over 4 years ago
Please note that it may not be possible to go though all topics that are raised in this agenda because we will discuss 2.8/3.0 release schedule. (Perhaps, we will prioritize the topics related to 2.8/3.0, such as Ractor.) Thanks.
Updated by marcandre (Marc-Andre Lafortune) over 4 years ago
- [Feature #16989] Sets need ♥️, aka the "Set Program" (marcandre)
- Bring
Set
into core - Insure interoperability with
Array
(e.g soarray & set
works and is efficient) - Shorthand syntax for static frozen sets of string/symbols (e.g.
%ws{hello world}
)
- Bring
Updated by jeremyevans0 (Jeremy Evans) over 4 years ago
- [Feature #17055] Allow suppressing uninitialized instance variable and method redefined verbose mode warnings (jeremyevans0)
- This keeps the default behavior the same as before, but allows opt-in to supress the warnings.
- This allows for high-performance code (uninitialized instance variables) and safe code (redefining methods without removing in multi-thread environments) to work without issuing warnings in verbose mode.
- Is it OK to commit the patch?
Updated by Eregon (Benoit Daloze) over 4 years ago
- [Feature #14844] Future of RubyVM::AST? (eregon)
- Other Ruby implementations need to be able to implement it too given more and more gems use it. Where do we move it?
- [Feature #15752] A dedicated module for experimental features (eregon)
- Create
ExperimentalFeatures
and move things there orRubyVM
exists on all Ruby implementations? Please choose.
- Create
Updated by Dan0042 (Daniel DeLorme) over 4 years ago
- [Bug #17017] Range#max & Range#minmax incorrectly use Float end as max (dan0042)
-
(1..3.1).max
has resulted in3.1
since ruby 1.9 and has now been "fixed" to return3
. Matz, please confirm?
-
Updated by byroot (Jean Boussier) over 4 years ago
- [Feature #17103] Add a :since option to
ObjectSpace.dump_all
(byroot)- On large heap,
dump_all
can take over a minute and generate huge (6+GiB) files. -
since: 42
, means only objects matchinggeneration && generation >= 42
would be dumped. - Sometimes you are only interested in objects allocated past a certain point, this make that use case much faster and efficient.
- On large heap,
Updated by Eregon (Benoit Daloze) about 4 years ago
- [Feature #17104] Do not freeze interpolated strings when using frozen-string-literal (eregon)
- It seems many people agree there is no point to freeze interpolated strings.
- Interpolated strings are not "simple literals" (just like
1 + 2
is not a literal) and they involve mutation anyway, it seems of very little value to freeze, and it's inconvenient. - @bughit (bug hit): The reasons are, it will reduce allocations, be more logical, less surprising and produce simpler code (when a mutable string is needed and you don't want extra allocations)
Updated by byroot (Jean Boussier) about 4 years ago
- [Feature #13381] Expose rb_fstring and its family to C extensions
- It's only missing a decision on the names. Could this be discussed again?
Updated by Eregon (Benoit Daloze) about 4 years ago
- [Bug #17105] A single
return
can return to two different places in a proc inside a lambda inside a method (eregon)- Is current implementation correct? Should it not be a
LocalJumpError
if the surrounding lambda is no longer on stack?
- Is current implementation correct? Should it not be a
Updated by znz (Kazuhiro NISHIYAMA) about 4 years ago
- [Feature #17125] Remove
Thread.exclusive
(znz)-
Thread.exclusive
is deprecated since 2.3.
-
Updated by mame (Yusuke Endoh) about 4 years ago
- [Feature #17122] Add category to Warning#warn (mame)
- I'd like to hear opinions from the committers
Updated by mrkn (Kenta Murata) about 4 years ago
- [Feature #14723] python's buffer protocol clone (mrkn)
- I renamed
buffer
tomemory_view
.- This name is already used in Python for the Python object wrapper of
PyBuffer
.
- This name is already used in Python for the Python object wrapper of
- I've added tests for some functions and a simple memory view implementation of a String for testing these functions.
- I renamed
Updated by mrkn (Kenta Murata) about 4 years ago
-
[Feature #16812] Allow slicing arrays with ArithmeticSequence (mrkn)
-
I found the wrong test case, so the implementation was also in wrong state. The proposed patch has been fixed.
-
There are opposing opinions in the following case:
[0,1,2,3,4,5][(6..0)%-2] #=> [5, 3, 1] # or [0,1,2,3,4,5][(6..0)%-2] #=> [4, 2, 0]
-
Python follows the former.
>>> [0, 1, 2, 3, 4, 5][6::-2] [5, 3, 1]
-
Updated by mame (Yusuke Endoh) about 4 years ago
The meeting was postponed to the next Monday (31th Aug.) for some reason.
Updated by duerst (Martin Dürst) about 4 years ago
- Subject changed from DevelopersMeeting20200826Japan to DevelopersMeeting20200831Japan
Adjust subject to match new date.
Updated by mame (Yusuke Endoh) about 4 years ago
- Description updated (diff)
- Status changed from Open to Closed