Please comment 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 ticket comments)
DO NOT discuss then on this ticket, please.
Date: 2018/09/13 (Thu)
Time: 14:00-18:00 (JST)
Place: Cookpad Inc. (Tokyo, Japan)
Past meetings: https://bugs.ruby-lang.org/projects/ruby/wiki#Developer-Meetings
- 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 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 is scheduled according to when/where we can reserve Matz's time.
About 2.6 timeframe¶
Carry-over from previous meeting(s)¶
(will be edited later)
(if you have a write access permission, please list directly)
- [Misc #14956] Remove staled branches in svn repository (hsbt)
- [Feature #6823] Where/how should ruby-mode issues be reported? (kazu)
(will be edited later)
(if you have a write access, please list directly)
Please comment 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 about it.
* [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 about this feature.
I don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).
Updated by mame (Yusuke Endoh) about 2 years ago
- [Feature #15022] Oneshot coverage
- I'd like to introduce a new kind of coverage to record whether each line is executed or not. It provides less but still useful information compared to the traditional line coverage, and the measurement is quite faster.
Updated by ioquatix (Samuel Williams) about 2 years ago
- [Feature #14975] String#append without changing receiver's encoding (ioquatix)
- Can we review this PR? We need to decide functionality (i.e. not changing receivers encoding, rejecting encoding if it's not same, unless receiver is binary).
- Longer term, we should consider if
concatshould be modified. Changing receiver's encoding seems like a mistake.
- [Feature #14739] Improve fiber yield/resume performance (ioquatix)
- Can I get commit access and can we agree to merge this change?
- [Feature #14888] Add trace point for eval (and related functions) (ioquatix)
- Can we decide if this is acceptable so I can make PR?
Updated by ana06 (Ana Maria Martinez Gomez) about 2 years ago
- [Feature #14097] Add union and difference methods to Array (ana06 (Ana Maria Martinez Gomez))
- Addition of two new methods in aim of readability, ease of use, efficiency and consistence. There are already PR for both methods.
- matz (Yukihiro Matsumoto) told me to add this here ;) After my talk in EuRuKo and the feedback from the standing voting I hope it is clearer and easy to decide if this is wanted
Updated by chopraanmol1 (Anmol Chopra) about 2 years ago
- [Bug #14908] Enumerator::Lazy creates unnecessary Array objects
- Proposed solution is to change arity of Enumerator::Yielder#<< to 1 from -1 and use it internally for lazy enum instead of Enumerator::Yielder#yield. Generally, method << is used with only one parameter changing arity to 1 also makes it consistent with other classes (String, Array)
- Since, proposed solution involves spec changes (Enumerator::Yielder#<<'s arity) a discussion is requested before the provided patch can proceed.
Updated by ahorek (Pavel Rosický) about 2 years ago
- [Feature #13167] Dir.glob is 25x slower since Ruby 2.2 (ahorek)