Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114469
MIME-Version: 1.0
References: <f3d20496-c560-42b7-9a0d-8672b3cafa7d@www.fastmail.com> <CAB-BujadPQ85-j6NA3gz5xOCptbZXKe0qPWkRUMfkMnft9e+4w@mail.gmail.com>
In-Reply-To: <CAB-BujadPQ85-j6NA3gz5xOCptbZXKe0qPWkRUMfkMnft9e+4w@mail.gmail.com>
Date: Thu, 13 May 2021 15:30:50 -0500
Message-ID: <CAESVnVoLmmUD2H7evyOs=rPnYR3+05TNS546SOFZigs2jE7Aww@mail.gmail.com>
To: Andreas Hennings <andreas@dqxtech.net>
Cc: Larry Garfield <larry@garfieldtech.com>, php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000072a35f05c23c0196"
Subject: Re: [PHP-DEV] [RFC] Partial function application
From: pollita@php.net (Sara Golemon)

--00000000000072a35f05c23c0196
Content-Type: text/plain; charset="UTF-8"

On Thu, May 13, 2021 at 2:31 PM Andreas Hennings <andreas@dqxtech.net>
wrote:

> 1. Serializing:
> But outside of the above cases it should be technically possible, or not?
>
>
I suspect that the limitations you cite make any kind of general
serializing both unreliable and impractical.  I wouldn't plan on meaningful
serialization.


> 2. var_export()
>
>
Same as above, really.


3. Parameter switching
>
> Could we express the following as a partial function?
>
> static function ($a, $b) {return foo($b, $a);}
>
> E.g. as foo(?1, ?0) ?
>
>
Using named parameter we can:

foo(b: ?, a: ?);

-Sara

--00000000000072a35f05c23c0196--