Issue #20075 has been updated by matheusrich (Matheus Richard).
* [Feature #13383] Module#source_location
- Matz
[
asked](https://github.com/ruby/dev-meeting-log/commit/9f106e4e484f6a512666d…
for specific use cases, so here are some:
- Debugging/Code Discovery: Similar to `Method#source_location`, it would be
useful to know where a module/class was defined (especially in large
codebases).
Doing a global search for `module Foo` is not always helpful because
nesting might make it harder to find the right one. It can also come from
a Gem.
This can help navigating new codebases much easier/faster.
- Documentation: It would be useful to know where a module/class was defined
when reading the documentation. RDoc could use this to list all the places
where a module/class was defined.
- I think we should list all the locations, so it should be `Module#source_locations`
----------------------------------------
Misc #20075: DevMeeting-2024-01-17
https://bugs.ruby-lang.org/issues/20075#change-106005
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2024/01/17 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 2024/01/14. 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/