Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115276
To: internals@lists.php.net
References: <CAF+90c--_H+=2yqkLKkFyGhKhwVJUJS8iRWw+hbZaSW1_q0xHw@mail.gmail.com>
Message-ID: <802fdb7d-69e5-edfa-de94-70416f9093d0@ralphschindler.com>
Date: Fri, 2 Jul 2021 11:31:53 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
 Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <CAF+90c--_H+=2yqkLKkFyGhKhwVJUJS8iRWw+hbZaSW1_q0xHw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [VOTE] First-class callable syntax
From: ralph@ralphschindler.com (Ralph Schindler)


> This RFC uses a syntax that is forward-compatible with partial function
> application. Should it not be accepted, I'll explore alternative syntax
> possibilities.

Given the choice of syntax in this proposal (which I do like)... Is the 
following (potentially future) use case precluded by the syntax (whether 
or not you like it immediately ;) )?

Basically be able to:

1. be able to refer to an instance method statically (this is currently 
an error)

2. allow late binding of $this/context/closure scope, either via 
bindTo() or via Reflection setClosureThis() (does not exist)



   class MyController {
     public function myAction($name) {
       return new Response("Hello, $name");
     }
   }

   // Closure with no $this (to be filled in later)
   $fn = MyController->myAction(...);


   $controller = new MyController;
   $response = ($fn->bindTo($controller))($params);



-ralph