Actions
Misc #19858
closedDevMeeting-2023-09-14
    Misc #19858:
    DevMeeting-2023-09-14
  
Status:
Closed
Assignee:
-
Description
The next dev meeting¶
Date: 2023/09/14 13:00-17:00 (JST)
Log: TBD
- 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/09/11. 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) about 2 years ago
          Updated by mame (Yusuke Endoh) about 2 years ago
          
          
        
        
      
      - Related to Misc #14770: [META] DevelopersMeeting added
        
           Updated by kyanagi (Kouhei Yanagita) about 2 years ago
          Updated by kyanagi (Kouhei Yanagita) about 2 years ago
          
          
        
        
      
      - [Feature #19075] Binary searching for the last element (kyanagi)
- My latest pull request implements bsearch(target: :last)andbsearch_index(target: :last).
- https://bugs.ruby-lang.org/issues/19075#note-6
- argument name?: target: :last,find: :last,reverse: true, ...
- separate method or not?: bsearch_last,reverse_bsearch,rbsearch, ...
 
- My latest pull request implements 
        
           Updated by nobu (Nobuyoshi Nakada) about 2 years ago
          Updated by nobu (Nobuyoshi Nakada) about 2 years ago
          
          
        
        
      
      - [Bug #19868] Process::Statusmethods for compatibility withFixnum(nobu)- Looking at 54274b8c65a0981f1c69055a1513ba3c614dd675, noticed that pst_rshiftcontains shift by a negative integer, an unspecified behavior in C99.
- I think an exception would be ok for such argument, also we can suggest alternative methods to encourage the transition.
- https://github.com/ruby/ruby/pull/8392
 
- Looking at 54274b8c65a0981f1c69055a1513ba3c614dd675, noticed that 
        
           Updated by jeremyevans0 (Jeremy Evans) about 2 years ago
          Updated by jeremyevans0 (Jeremy Evans) about 2 years ago
          
          
        
        
      
      - [Bug #17146] Queue operations are allowed after it is frozen (jeremyevans0)
- Last discussed at October 2020 developer meeting, no decision made.
- @headius (Charles Nutter) and I discussed this at RubyKaigi and agreed it would be best to raise FrozenError for push/pop for frozen queues.
- Can we either decide this is a bug and fix it, or decide it is not and close it?
 
- [Bug #17354] Module#const_source_location is misleading for constants awaiting autoload (jeremyevans0)
- Last discussed at March 2021 developer meeting, no decision made.
- I agree the method result is misleading, but as @mame (Yusuke Endoh) states in note 10, current design is the most flexible.
- Can we either decide this is a bug and fix it, or decide it is not and close it?
 
- [Bug #7964] Writing an ASCII-8BIT String to a StringIO created from a UTF-8 String (jeremyevans0)
- Do we want StringIO to handle encoding?
- Making it handle encoding makes it more like IO, fixing some existing compatibility issues but introducing new compatibility issues.
 
- [Bug #9115] Logger traps all exceptions; breaks Timeout (jeremyevans0)
- Can we fix this by supporting specific exception classes to reraise instead of swallow?
- If not, is there an alternative approach that would be acceptable to fix this?
 
        
           Updated by mame (Yusuke Endoh) about 2 years ago
          Updated by mame (Yusuke Endoh) about 2 years ago
          
          
        
        
      
      - Status changed from Open to Closed
Actions