Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106531
To: Mark Randall <markyr@gmail.com>, internals@lists.php.net
References: <CAF+90c95GBUbbWUDhP2jW1q9uK3cnEomcwN7xWAup=PhJ0+S1Q@mail.gmail.com>
 <php.internals-106529@news.php.net>
Message-ID: <050e85c8-449f-67f5-566e-a1e4929ef0cd@gmx.de>
Date: Sat, 10 Aug 2019 18:11:47 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <php.internals-106529@news.php.net>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: quoted-printable
Subject: Re: Call for participation: Annotating internal function
 argumentandreturn types
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 10.08.2019 at 17:54, Mark Randall wrote:

> On 10/08/2019 11:56, Nikita Popov wrote:
>
>> Lack of type information for internal functions in Reflection is a
>> long-standing issue. In PHP 8 we finally have all the necessary technic=
al
>> groundwork done to support argument and return type annotations on
>> internal
>> functions at scale.
>
> Question - If every function needs looking through and parsing, would
> this be a suitable time to move from the ZPP varadic to the macros?

In my opionion, we should only use the macros if the performance
improvement matters for the function at hand; otherwise the increased
memory footprint of the macros unnecessarily bloats the executables.

Thanks,
Christoph