The next dev meeting¶
Date: 2020/08/26 13:00-17:00
- 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.)
* [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 marcandre (Marc-Andre Lafortune) 15 days ago
- [Feature #16989] Sets need ♥️, aka the "Set Program" (marcandre)
- Insure interoperability with
array & setworks and is efficient)
- Shorthand syntax for static frozen sets of string/symbols (e.g.
Updated by jeremyevans0 (Jeremy Evans) 9 days 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) 5 days 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)
ExperimentalFeaturesand move things there or
RubyVMexists on all Ruby implementations? Please choose.
Updated by byroot (Jean Boussier) 2 days ago
- [Bug #17020]
ObjectSpace.trace_object_allocations_stopraises if called before
- It's a minor bug, but requires some annoying workarounds.
- [Feature #17103] Add a :since option to
- On large heap,
dump_allcan take over a minute and generate huge (6+GiB) files.
- 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) 34 minutes 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 + 2is 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)