Re: [VOTE] First-class callable syntax
| From: | Sara Golemon | Date: | Mon, 05 Jul 2021 14:14:46 +0000 |
| Subject: | Re: [VOTE] First-class callable syntax | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-115302@lists.php.net to get a copy of this message | ||
On Fri, Jul 2, 2021 at 5:51 AM Nikita Popov <nikita.ppv@gmail.com> wrote:
> As the partial function application RFC has not been accepted, I have
> opened voting on
> https://wiki.php.net/rfc/first_class_callable_syntax. The
> vote closes on 2021-07-16.
>
> This RFC uses a syntax that is forward-compatible with partial function
> application. Should it not be accepted, I'll explore alternative syntax
> possibilities.
>
>
Was replying to a comment on reddit which made me look closer at your
implementation. It looks like this does NOT allow for use of function-like
language constructs.
e.g. $e = echo(...); $p = print(...); $r = require(...); // etc...
1/ Is this intentional?
2/ Is this actually a good thing?
I'm actually of a mind that it's a good thing, as surprising ways to reach
eval() are foot-guns waiting to happen, but wanted to get confirmation.
-Sara