Misc #15546
Updated by Eregon (Benoit Daloze) almost 6 years ago
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/02/07 (Thu)
Time: 13:00-17:00 (JST)
Place: MoneyForward.com (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/117659/
log: https://docs.google.com/document/d/e/2PACX-1vRbZsyab3LFwhcti973QNpaifVgdJHdxu00V0qdXk6EPv76OzfPRbqQHyUqIVhlWF7-HBv0QiIivrQ2/pub
logedit: https://docs.google.com/document/d/1U498rgriOF4094D9UKBJyjt0PFzXFvGSvMqLjci2AN8/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)
## From Attendees
## From non-attendees
* [Feature #6470] Make attr_accessor return the list of generated method (eregon)
* I think not all related issues were considered. There are use cases, both for private attr_* and other modifiers (e.g., volatile, atomic, tracing accesses, getter/setter decorators, etc).
* [Bug #14353] $SAFE should stay at least thread-local for compatibility (eregon)
* I would like matz's opinion on this. It seems the compatibility risks and debugging problems is not worth making $SAFE global, unless there is a good reason to be global? Should there still be $SAFE checks at all, for e.g., tainted Strings?
* [Feature #5653] "I strongly discourage the use of autoload in any standard libraries" (eregon)
* Could we have a decision for this? What does it gain, and at what cost for compatibility? Is there going to be a replacement?
----
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).