Project

General

Profile

Actions

Misc #17734

closed

DevelopersMeeting20210416Japan

Added by mame (Yusuke Endoh) about 2 months ago. Updated 29 days ago.

Status:
Closed
Priority:
Normal
Assignee:
-
[ruby-core:102934]

Description

The next dev meeting

Date: 2021/04/16 13:00-17:00
Place/Sign-up/Agenda/Log: https://github.com/ruby/dev-meeting-log/blob/master/DevelopersMeeting20210416Japan.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 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.)

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 2021/04/13. 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

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

Updated by mame (Yusuke Endoh) about 2 months ago

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

Updated by jeremyevans0 (Jeremy Evans) about 1 month ago

  • [Bug #17398] SyntaxError in endless method (jeremyevans0)
    • I don't believe this is a bug, but maybe it is a useful feature.
    • mame (Yusuke Endoh) has a patch that allows commands as the RHS of a endless method.
    • However, mame (Yusuke Endoh)'s patch doesn't allow direct usage with method visibility methods such as private.
    • Do we want to support this syntax, or can this be closed (or moved to Feature)?
  • [Bug #17403] Remove Fixnum and Bignum (jeremyevans0)
    • Do we want to remove Fixnum and Bignum in Ruby 3.1?
    • If not, can we decide on a later version where they can be removed, such as 3.2 or 4.0?
  • [Bug #16983] RubyVM::AbstractSyntaxTree.of(method) returns meaningless node if the method is defined in eval (jeremyevans0)
    • RubyVM::AbstractSyntaxTree.of(method) relies on reading the file with the method source, which could have changed or could not exist at all.
    • I don't think we can work around that without keeping the abstract syntax tree or source code of all methods in memory, which seems wasteful.
    • Is the current behavior a bug, or should we just accept the current behavior as spec and close this?
  • [Bug #9542] Delegator does not delegate protected methods (jeremyevans0)
    • Do we want to add a way to tell if a method was called with an implicit receiver or self?
    • We may be able to implement this via a VM frame flag and a method to check it.
    • If we don't want to add such a way, can we accept the current behavior as spec and close this?
  • [Bug #11230] Should rb_struct_s_members() be public API? (jeremyevans0)
    • This is still public in the C-API.
    • Do we want to keep it and close this issue, or do we want to remove it?
    • If we want to remove it, how should it be deprecated?

Updated by tenderlovemaking (Aaron Patterson) about 1 month ago

  • [Feature #17749] Add Module#source_location
    • It's similar to the const_source_location feature, but easier to use when you don't know the constant name, or enclosing const
    • This is useful for debugging
  • [Feature #17753] Add Module#namespace
    • A::B.namespace will return A
    • This is to help with finding "sibling" constants of B so we don't have to parse the constant name
    • This is also useful for debugging

Updated by mame (Yusuke Endoh) about 1 month ago

  • [Feature #17762] A simple way to trace object allocation
    • I want require "objspace/trace" or something which is a very useful debugging tool to identify the allocation site of an object.

Updated by Dan0042 (Daniel DeLorme) about 1 month ago

  • [Feature #17682] String#casecmp performance improvement (dan0042)
    • Is it ok to make casecmp faster?

Updated by marcandre (Marc-Andre Lafortune) about 1 month ago

  • [Feature #15198] Add Array#intersect? (marcandre)
    • Ok to add?

Updated by byroot (Jean Boussier) about 1 month ago

  • [Feature #17795] before_fork and after_fork callback API
    • Many libraries out there use various tricks to detect the process being forked, most commonly Process.pid != @pid, but glibc no longer cache the PID so these libraries end up doing syscalls in tight loops.
    • If a callback API is too complicated, I proposed a simplee alternative that is to have Kernel.fork be a simple delegator to Process.fork https://github.com/ruby/ruby/pull/4361, This would makes it easy for libraries to decorate fork to have their own callbacks on either before or after fork.

Updated by parker (Parker Finch) about 1 month ago

  • [Feature #17016] Add Enumerable#accumulate (parkerfinch)
    • Is the name #accumulate acceptable?
    • Is this feature ok to add?
Actions #9

Updated by mame (Yusuke Endoh) 29 days ago

  • Status changed from Open to Closed
  • Description updated (diff)
Actions

Also available in: Atom PDF