Project

General

Profile

Actions

Misc #19883

closed

DevMeeting-2023-10-12

Added by mame (Yusuke Endoh) about 1 year ago. Updated about 1 year ago.

Status:
Closed
Assignee:
-
[ruby-core:114773]

Description

The next dev meeting

Date: 2023/10/12 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/10/09. 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.

Related issues 1 (1 open0 closed)

Related to Ruby master - Misc #14770: [META] DevelopersMeetingOpenActions
Actions #1

Updated by mame (Yusuke Endoh) about 1 year ago

  • Related to Misc #14770: [META] DevelopersMeeting added

Updated by tagomoris (Satoshi Tagomori) about 1 year ago

  • [Feature #19744] Namespace on read (tagomoris)
    • Now the PoC implementation works, can require 2 different versions of native extension libraries.
    • I will introduce the motivation and the implementation idea.
    • I need discussions about:
      • Several design decision points
      • APIs for apps
      • Migration paths

Updated by jeremyevans0 (Jeremy Evans) about 1 year ago

  • [Feature #18573] Object#pack1 (jeremyevans0)
    • For the same reason as String#unpack1, saves an array allocation when packing a single object.
    • I think it would be useful to have this feature, but I prefer Array.pack1 to Object#pack1 to implement it.
    • Can we add this feature, and if so, do we want to use Array.pack1, Object#pack1, or a different method for it?
  • [Bug #19866] Future of readline.rb (jeremyevans0)
    • Seems odd for a standard library to attempt to load a non-standard library first, and fallback to loading a standard library.
    • Are we OK with how lib/readline.rb currently works? If so, we can close this.
  • [Bug #16927] String#tr won't return the expected result for some sign with diacritics (jeremyevans0)
    • Do we plan to convert String#tr (and potentially other String methods) from operating on codepoints to operating on grapheme clusters at some point?
  • [Bug #18903] Stack overflow signal handling seems to be triggered once and then not working after (jeremyevans0)
    • Should we raise fatal error instead of SystemStackError for stack overflows in C code?
    • VM stack overflow can be safely rescued, since we check for the stack overflow before overflowing.
    • C stack overflow cannot be safely rescued in all cases.

Updated by kyanagi (Kouhei Yanagita) about 1 year ago

  • [Misc #18984] Doc for Range#size for Float/Rational does not make sense (kyanagi)
    • Range#size may return a non-nil value even if the range can't be iterated.
    • Should it return nil?
  • [Feature #18515] Add Range#reverse_each implementation (kyanagi)
    • This enables #reverse_each for huge or beginless ranges.
    • If this is acceptable, [Feature #18551] should also be considered.
  • [Feature #18551] Make Range#reverse_each to raise an exception if endless (kyanagi)

Updated by Dan0042 (Daniel DeLorme) about 1 year ago

  • [Feature #13933] Add Range#empty?
    • "empty?" is a basic concept for core classes
    • Related to the implementation of Range#overlap? (empty_region_p) so why not make it a public interface?
    • For beginless ranges we cannot use (..0).none?
    • For string ranges we cannot use ("a".."b").size
    • There's an edge case with e.g. (...-Float::INFINITY) or (..."") with several possible approaches listed in the ticket

Updated by yui-knk (Kaneko Yuichiro) about 1 year ago

  • [Bug #19919] Variable assignments in condition are warned however class variable assignment and constant declaration are not warned
    • Is it better to warn class variable assignment and constant declaration ?
Actions #7

Updated by jeremyevans0 (Jeremy Evans) about 1 year ago

  • Status changed from Open to Closed
Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0Like0Like0Like0