Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112217
MIME-Version: 1.0
References: <CA+kxMuRjJ5B_ykNXeMZhAd6iduh-VEk7CNP0vNuZp9fjka5_HQ@mail.gmail.com>
In-Reply-To: <CA+kxMuRjJ5B_ykNXeMZhAd6iduh-VEk7CNP0vNuZp9fjka5_HQ@mail.gmail.com>
Reply-To: Levi Morrison <levi.morrison@datadoghq.com>
Date: Tue, 10 Nov 2020 10:18:31 -0700
Message-ID: <CAAKU0u=cHBO1r=vA9_KdXzrPGzQuiCksPTPYZZB5d0mSfrDxfw@mail.gmail.com>
To: Dan Ackroyd <Danack@basereality.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] Draft - Closure self reference
From: internals@lists.php.net ("Levi Morrison via internals")

On Tue, Nov 10, 2020 at 10:09 AM Dan Ackroyd <Danack@basereality.com> wrote:
>
> Hello internals,
>
> For reasons, I was reviewing the conversation where adding closures to
> PHP was added, and it reminded me that currently the only way for a
> closure to call itself is slightly terribly, so I drafted an RFC:
>
> https://wiki.php.net/rfc/closure_self_reference
>
> Before I spend time on it, is there any strong reason why this is a bad idea?
>
> cheers
> Dan
> Ack
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php

Is there any way we can we spell it `__FUNCTION__`?