Actions
Misc #19429
closedDevMeeting-2023-03-09
Status:
Closed
Assignee:
-
Description
The next dev meeting¶
Date: 2023/03/09 13:00-17:00 (JST)
Log: https://github.com/ruby/dev-meeting-log/blob/master/2023/DevMeeting-2023-03-09.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 record of the discussion in the 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 of the meeting 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.
- It is recommended to add a comment by 2023/03/06. We hold a preparatory meeting to create an agenda a few days before the dev-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. We appreciate it if you could write a short summary and update from a previous discussion.
Updated by mame (Yusuke Endoh) over 1 year ago
- Related to Misc #14770: [META] DevelopersMeeting added
Updated by sawa (Tsuyoshi Sawada) over 1 year ago
- [Feature #10343] Postfix notations for
when
andelse
insidecase
statement (sawa)- Allow
foo when condition
within case-statements. - Has not received feedback for eight years.
- Allow
Updated by zverok (Victor Shepelev) over 1 year ago
- [Bug #19362]
#dup
onProc
doesn't callinitialize_dup
(zverok)- The fact that
initialize_dup
is not called byProc#dup
is inconsistent, and there are no docs confirming it is deliberate. @nobu's PR shows it is possible to fix.
- The fact that
Updated by byroot (Jean Boussier) over 1 year ago
- [Feature #19435] Expose counts for each GC reason in GC.stat
- Add 8 new keys in
GC.stat
. - We used that patch in production to fix GC issues we had, we believe these counters to be high value.
- The only way to get this information today is to compile with debug counters, which isn't very suitable.
- Add 8 new keys in
Updated by AMomchilov (Alexander Momchilov) over 1 year ago
- [Feature #19197] Add
Exception#root_cause
(AMomchilov)- It returns the last exception in linked-list of causality chain, that is, the original exception (whose own cause is
nil
).
- It returns the last exception in linked-list of causality chain, that is, the original exception (whose own cause is
Updated by Eregon (Benoit Daloze) over 1 year ago
- [Feature #19440] Deprecate ThreadGroup (eregon)
- Thoughts?
- If disagree, how do we put the Timeout thread in the default ThreadGroup? It seems impossible with current API.
Updated by byroot (Jean Boussier) over 1 year ago
- [Bug #19436] Call Cache for singleton methods can lead to "memory leaks" (byroot)
- When caching a singleton method call, the receiver becomes immortal until that call cache is updated.
- On large apps with some infrequently called codepaths this can lead to very large objects graphs not being collected.
- The reference chain is
IMEMO(callcache) -> IMEMO(ment) -> ICLASS -> CLASS(singleton) -> OBJECT
- I explored 3 solutions
- Only keep a weak reference to the CME
- Don't cache singleton method calls (unless it's a Class or Module singleton)
- Make Class#attached_object a weak reference
- I'd like to get opinions on which solution would be preferable.
Updated by eightbitraptor (Matt V-H) over 1 year ago
- [Feature #19406] Allow declarative reference definition for rb_typed_data_struct (eightbitraptor)
- This is essentially a simpler interface for handling marking/compaction for
rb_typed_data_struct
that hold references to other Ruby objects than the existingdmark
/dcompact
callback interface. - It's useful in non-complex cases where the object just holds simple reference. Is this enough for it to have value?
- This is essentially a simpler interface for handling marking/compaction for
Updated by peterzhu2118 (Peter Zhu) over 1 year ago
- [Feature #19437] Add marking and sweeping time to GC.stat (peterzhu2118)
- This feature records GC time in marking and sweeping phases and exposed them via a
marking_time
andsweeping_time
key inGC.stat
. - This feature will allow us to know the proportion of time spent in each phase of GC to help us better tune the GC.
- This means that
GC.stat(:time) == GC.stat(:marking_time) + GC.stat(:sweeping_time)
.
- This feature records GC time in marking and sweeping phases and exposed them via a
Updated by ioquatix (Samuel Williams) over 1 year ago
- [Feature #19450] Is there an official way to set a class name without setting a constant?
- Do we accept
Class.new(superclass, name)
andModule.new(name)
syntax?
- Do we accept
- [Feature #19451] Extract path and line number from
SyntaxError
?- Can we introduce
SyntaxError#column
or similar interface?
- Can we introduce
- [Feature #19452]
Thread::Backtrace::Location
should have column information if possible.- Can we introduce
Thread::Backtrace::Location#column
or similar interface?
- Can we introduce
- [Feature #19094]
sleep(nil)
vssleep()
and replicating the default implementation.- Do we accept
sleep(nil)
is equivalent tosleep()
?
- Do we accept
Updated by jeremyevans0 (Jeremy Evans) over 1 year ago
- [Bug #19455] Ruby 3.2: wrong Regexp encoding with non-ASCII comments (jeremyevans0)
- Is using US-ASCII encoding for such regexps a bug? Since the regexp itself does not use non-ASCII, it seems reasonable to use ASCII encoding for the regexp.
- For such regexps, even if the regexp itself is US-ASCII, should the source still be UTF-8, since the source contains non-ASCII characters?
- Are there issues if the regexp encoding does not match the source encoding, because the non-ASCII characters are in comments?
- [Bug #19417] Regexp \p{Word} and
[[:word:]]
do not match Unicode Other_Number character (jeremyevans0)- Is this a documentation bug or a code bug?
- If a documentation bug, how specific should the documentation be about what \p{Word} and
[[:word:]]
match?
- [Bug #19392] Endless method vs and/or (jeremyevans0)
- Is this a bug or expected behavior?
- [Bug #19416] Inconsistent behaviour for Struct.new without any member_names (jeremyevans0)
- The fact that Struct.new("A") works seems like a bug and not intentional.
- Do we want to fix the bug, or keep it to retain backwards compatibility?
- If we want to fix it, should we deprecate or remove the support in 3.3?
Updated by ko1 (Koichi Sasada) over 1 year ago
- [Feature #19472] Ractor::Selector to wait multiple ractors (ko1)
- let me take a time to discuss about new Ractor synchronization API
Updated by mame (Yusuke Endoh) over 1 year ago
- [Bug #19230] The openssl backend of securerandom is no longer needed
- The openssl backend of securerandom has not worked for several years, but we have received no bug reports. I think no one uses it. Let's remove the backend.
Updated by Eregon (Benoit Daloze) over 1 year ago
- [Bug #19473] can't be called from trap context (ThreadError) is too limiting (eregon)
- This seems a needless limitation on CRuby causing real problems. Let's remove this incorrect exception/limitation?
Updated by ko1 (Koichi Sasada) over 1 year ago
- [Bug #18743] Enumerator#next / peek re-use each others stacktraces (ko1)
- It should be a bug and there is a proposed patch.
Updated by mame (Yusuke Endoh) over 1 year ago
- Description updated (diff)
- Status changed from Open to Closed
Actions
Like0
Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0