Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115271
MIME-Version: 1.0
References: <1ae611cb-b077-3db0-3237-c7ffa1c6e745@ralphschindler.com>
In-Reply-To: <1ae611cb-b077-3db0-3237-c7ffa1c6e745@ralphschindler.com>
Date: Fri, 2 Jul 2021 09:00:35 +0430
Message-ID: <CAEMvS4F71AoaK5U1ZOw2SaSJVMA_EmE=ZfQubEMR7DOoeBRV-w@mail.gmail.com>
To: Ralph Schindler <ralph@ralphschindler.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000059f91705c61c6f13"
Subject: Re: [PHP-DEV] [Proposal] call_user_func_map(): flexible named
 parameter mapping for call_user_func*
From: hossein.baghayi@gmail.com (Hossein Baghayi)

--00000000000059f91705c61c6f13
Content-Type: text/plain; charset="UTF-8"

Hello,

On Sun, 27 Jun 2021 at 19:09, Ralph Schindler <ralph@ralphschindler.com>
wrote:

>
> This proposes a method for a publisher/framework/producer (the caller of
> the callback) to document all the parameters that are available as named
> parameters, and subscribers/consumers (creator of the callback) could
> subscribe to what they need by name.
>

Wouldn't it rather be nice if we had more detailed callable types instead?
I mean instead of simply defining a parameter type as `callable` we could
specifically define what the callable expects.

Something like this:
```
function bar ((int, string):bool $callback) {...}
```

A more generic approach that could be more descriptive, maybe.

I have no clue if this was already discussed in other threads or not. And
whether it is feasible to implement.

Regards,

--00000000000059f91705c61c6f13--