Re: Draft RFC callable types + callable type/functio n autoloading

On Wed, Jul 1, 2020, at 4:55 AM, Dan Ackroyd wrote: > On Tue, 26 May 2020 at 18:08, Iván Arias <txigreman@hotmail.com> wrote: > > Just a Little question. I see this other document in the same repo: > > > > > > https://github.com/Danack/FunctionTypes/blob/master/3_referencing_functions_and_callables.md > > > > Are you planning to also raise it? > > Yes, but for PHP 8.1. > > Although I think it's an important problem to solve, I don't actually > like it as a solution, for aesthetic reasons. > > I'm planning to draft it as an RFC right after the 8.0 RFCs close, > which will give people a year to come up with a better solution. > > cheers > Dan > Ack On a related tangent, which someone else suggested was relevant here: Levi Morrison wrote another RFC a while ago on partial function application: https://wiki.php.net/rfc/partial_function_application He hasn't had bandwidth to work on it, though. I have taken a stab at it, and mostly handed it over to Ilija Tovilo who has pushed it further along. It's not going to be ready for 8.0 by a long shot, but we're hoping to have it ready for 8.1. (Exact details to depend on the implementation, WIP.) Although it's not the main goal, it would also offer a way to do effectively the same thing as the direct callable reference RFC: https://wiki.php.net/rfc/partial_function_application#use_as_an_identifier It's not an ideal substitute, but it's close to one and wouldn't require a separate syntax. I mention it here mostly for transparency and to make sure we don't end up with multiple competing RFCs that duplicate functionality needlessly. --Larry Garfield