From: "shioyama (Chris Salzberg) via ruby-core" <ruby-core@...>
Date: 2023-05-09T08:40:56+00:00
Subject: [ruby-core:113431] [Ruby master Misc#19599] DevMeeting-2023-05-10 @ Matsumoto, Japan

Issue #19599 has been updated by shioyama (Chris Salzberg).


* [Feature #19633] `Allow passing block to `Kernel#autoload` as alternative to second `filename` argument`
  * Something like this would remove the need for Zeitwerk to monkeypatch `Kernel#require`
  * Connects autoloads directly to any callbacks on them, rather than having the connection be implicit via `require`. I think this is an improvement.
  * I am implementing autoloads on anonymous modules via a similar monkeypatch; this would make that monkeypatch unnecessary and simplify other logic via the block's closure.

----------------------------------------
Misc #19599: DevMeeting-2023-05-10 @ Matsumoto, Japan
https://bugs.ruby-lang.org/issues/19599#change-103003

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2023/05/10 14:00-17:00 @ ** (JST)
Location: [M2 meeting room](https://www.mpac.jp/guide/studio/?item=s-04) in [Matsumoto Performing Arts Centre](https://www.mpac-en.com/about) (Access to M2 meeting room: Please take the elevator on the left of the main entrance to the floor "M2", get off the elevator and go straight.)
Log: *TBD*
See also: https://bugs.ruby-lang.org/issues/19431


- 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/05/07. 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](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86).  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.




-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/