Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115272
Message-ID: <F7341F29-630D-4268-B98A-C1379763A36B@newclarity.net>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_C0AE5F8B-EF8E-4A4E-9CA7-BA02313F60B1"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Date: Fri, 2 Jul 2021 01:05:43 -0400
In-Reply-To: <CAEMvS4F71AoaK5U1ZOw2SaSJVMA_EmE=ZfQubEMR7DOoeBRV-w@mail.gmail.com>
Cc: PHP internals <internals@lists.php.net>
To: Hossein Baghayi <hossein.baghayi@gmail.com>
References: <1ae611cb-b077-3db0-3237-c7ffa1c6e745@ralphschindler.com>
 <CAEMvS4F71AoaK5U1ZOw2SaSJVMA_EmE=ZfQubEMR7DOoeBRV-w@mail.gmail.com>
Subject: Re: [PHP-DEV] [Proposal] call_user_func_map(): flexible named
 parameter mapping for call_user_func*
From: mike@newclarity.net (Mike Schinkel)

--Apple-Mail=_C0AE5F8B-EF8E-4A4E-9CA7-BA02313F60B1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii



> On Jul 2, 2021, at 12:30 AM, Hossein Baghayi =
<hossein.baghayi@gmail.com> wrote:
>=20
> Hello,
>=20
> On Sun, 27 Jun 2021 at 19:09, Ralph Schindler =
<ralph@ralphschindler.com>
> wrote:
>=20
>>=20
>> 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.
>>=20
>=20
> 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.
>=20
> Something like this:
> ```
> function bar ((int, string):bool $callback) {...}
> ```
>=20
> A more generic approach that could be more descriptive, maybe.
>=20
> I have no clue if this was already discussed in other threads or not. =
And
> whether it is feasible to implement.


=46rom 2015 which failed (not sure why):=20

https://wiki.php.net/rfc/callable-types

But I believe that would be better to be part of a broader ability to =
define our own types, e.g.

type function(int, string):bool IntStrFunc;
function bar (intStrFunc $callback) {...}

I think a few have mentioned user-defined types in the recent past but I =
am not aware of it being a current RFC for it.=20

-Mike=

--Apple-Mail=_C0AE5F8B-EF8E-4A4E-9CA7-BA02313F60B1--