Issue #15874 has been updated by byroot (Jean Boussier).


* [Feature #15777] `Module#autoload?(cname, inherit=true)`
  * By default `autoload?` also check in the ancestors chain, such option would be consistent with `Module#const_defined?` and totally backward compatible.
  * For more context this would be needed in Zeitwerk: https://github.com/fxn/zeitwerk/pull/17

* [Proposal #15836] Make `Module#name` and / or `Symbol#to_s` return their internal fstring.
  * I realize this is unlikely to be accepted because it has a very significant backward compatibility impact, but I'll still make a case for it.
  * It's surprising for both of these method to allocate new strings when intuitively we're accessing some static metadata.
  * These two method are extensively used in metaprogramming code and other DSL, they are responsible for a significant amount of allocations and duplications.
  * Ideally to address the backward compatibility issues, the behavior would only change if `frozen_string_literal: true` is set, but I'm unsure this is actually possible to implement.

----------------------------------------
Misc #15874: DevelopersMeeting20190613Japan
https://bugs.ruby-lang.org/issues/15874#change-78253

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment your favorite ticket numbers you want to ask to discuss with your *SHORT* comment or summary.
(your summary/comment will help us because we don't need to read all of ticket comments)

*DO NOT* discuss then on this ticket, please.

----

Date: 2019/06/13 (Wed)
Time: 14:00-17:30 (JST)
Place and Sign-up: https://ruby.connpass.com/event/132888/
log: https://docs.google.com/document/d/1XP_e-3utXlCaxZLJrov6c428ZNaMPmxa3eh9MASrzkI/edit#

# NOTES

- 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 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 is scheduled according to when/where we can reserve Matz's time.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

None.

## From Attendees

## From non-attendees

----

Please comment your favorite ticket we need to discuss with *the following format*.

```
* [Ticket ref] Ticket title (your name)
  * your comment why you want to put this ticket here if you want to add.
```

Your comment is very important if you are no attendee because we can not ask why you want to discuss about it.

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 about this feature.
```

We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>