Misc #15229

Updated by shyouhei (Shyouhei Urabe) 9 months 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: 2018/11/22 (Thu)
Time: 14:00-18:00 (JST)
Place: pixiv Inc. (Tokyo, Japan)


- 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.6 timeframe

## Check security tickets

## Carry-over from previous meeting(s)

## From Attendees

* [Feature #15230] RubyVM.resolve_feature_path (mame)
* I'd like this feature to investigate what will be loaded by require(feature).
* [Feature #15231] Remove `Object#=~` (mame)
* The method looks useless, and made a trouble at least for me. I'd like to hear opinions from other committers.
* [Feature #11689] Add methods allow us to get visibility from Method and UnboundMethod object. (yui-knk)
* I want to introduce this feature to help meta programming. I'd like to hear opinions from other committers.
* [Feature #15286] Proposal: Add Kernel.#expand(*args) (aycabta)
* [Feature #15289] Accept "target" keyword on `TracePoint#enable` (ko1)
* [Feature #15287] New TracePoint events to support loading features (ko1)
* [Bug #6087] How should inherited methods deal with return values of their own subclass? (mame)
* 6 years ago, matz decided that class A < Array; end; #=> A in 2.X, Array in 3.0. Just confirm: has the decision been still unchanged?

## From non-attendees

* [Bug #14127] CSV (CSV) generating UTF-16LE encoded file without BOM (nobu)
* Although this is not a bug of csv.rb, I'd suggest to enable "`bom|`" flag when writing instead.
* [Bug #15285] lambda return behavior regression from #14639 (nobu)
* [Feature #15220] Adding OpenSSL 1.1.1 on Travis CI gcc-8 case (jaruga)
* To detect an issue for the latest OpenSSL early and guarantee a Ruby version supporting a OpenSSL version.
* [Feature #15301] `Symbol#call`, returning method bound with arguments (zverok)
* [Feature #15302] Proc#with and Proc#by, for partial function application and currying (Ritchie Buitre)
* Convenient methods for functional programming.
* [Bug #14968] make all pipes and sockets non-blocking by default (normalperson)
* [Feature #13618] Thread::Light for 2.6 [ruby-core:89900] (normalperson)
* [Feature #15317] How to deal with obsolete property values in Unicode 11.0.0 (duerst)
* A clear idea on this is needed to upgrade to Unicode 11.0.0.
* [Feature #13890] Allow a regexp as an argument to 'count', to count more interesting things than single characters (duerst)
* I find this missing regularly, and writing it by hand in Ruby is clumsy, so addition would be valuable.
* [Feature #12698] Method to delete a substring by regex match (duerst)
* [Feature #10548] remove callcc (Callcc is now going obsoleted. Please use Fiber.) (ioquatix)
* It's unofficially deprecated, unsupported in most implementations of Ruby, and not used very much. Do you think it's a good idea to drop support by 3.0?
* [Feature #15327] Proposal: Enable refinements to `#respond_to?` (osyo)
* [Feature #15326] Proposal: Enable refinements to `#public_send` (osyo)
* [Feature #15114] Symbol#to_proc does not work with refinements? (osyo)
* I want to more refinements!
* [Feature #15330] Proposal: autoload_relative (marcandre)
* This feature is actually more useful than autoload and should be added to 2.6


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.


* [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.

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