Issue #17535 has been updated by mrkn (Kenta Murata).


* [Feature #17291] Optimize `__send__` call (mrkn)
  * [rspec-mocks](https://github.com/rspec/rspec-mocks) depends on redefining `__send__` to detect the form of the method call in a mock object.
  * The mock object raises NoMethodError when the method call form is `obj.method` and the called method is not public.
    * This behavior occurs the following step:
      1. [Keeping the method name at `__send__` and `send` in mock object](https://github.com/rspec/rspec-mocks/blob/c1a86de005c5aa7885dbc92487422b0c0f43d324/lib/rspec/mocks/verifying_double.rb#L45-L57)
      1. [Check the method called via `__send__` at `method_missing`](https://github.com/rspec/rspec-mocks/blob/c1a86de005c5aa7885dbc92487422b0c0f43d324/lib/rspec/mocks/verifying_double.rb#L20-L35)
      1. [Check the method visibility in `ensure_publicly_implemented`](https://github.com/rspec/rspec-mocks/blob/c1a86de005c5aa7885dbc92487422b0c0f43d324/lib/rspec/mocks/verifying_proxy.rb#L48-L54)
      1. [Raise `NoMethodError` in `raise_non_public_error`](https://github.com/rspec/rspec-mocks/blob/c1a86de005c5aa7885dbc92487422b0c0f43d324/lib/rspec/mocks/error_generator.rb#L111-L115)
  * The new feature to detect the method call form is necessary to keep this behavior when we introduce this optimization of `__send__`.

----------------------------------------
Misc #17535: DevelopersMeeting20210216Japan
https://bugs.ruby-lang.org/issues/17535#change-89933

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

**Date: 2021/02/16 13:00-17:00**
Place/Sign-up/Agenda/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 log about the 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 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 2021/02/13. 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/

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