Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104177
MIME-Version: 1.0
References: <CAF+90c9E6O-12fKKY_kb5b_LvXgODbPpC73TNro+XpMewndT2Q@mail.gmail.com>
In-Reply-To: <CAF+90c9E6O-12fKKY_kb5b_LvXgODbPpC73TNro+XpMewndT2Q@mail.gmail.com>
Date: Tue, 5 Feb 2019 13:23:20 +0100
Message-ID: <CAFPFaMLY6kebV9d=J4ZxGc5-gm2X=57knbaOnoum1FzpZccMvQ@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000096f808058124ad3e"
Subject: Re: [PHP-DEV] [RFC] Consistent type errors for internal functions
From: george.banyard@gmail.com (Girgias)

--00000000000096f808058124ad3e
Content-Type: text/plain; charset="UTF-8"

On Tue, 5 Feb 2019 at 12:22, Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals,
>
> I'd like to bring forward the following proposal for PHP 8, which will make
> (zpp) parameter parsing failures always result in a TypeError (rather than
> generating a warning+null, depending on circumstances):
>
> https://wiki.php.net/rfc/consistent_type_errors
>
> The goal here is to remove one of the inconsistencies between user-defined
> and internal functions, and to put us in a position where we can actually
> start specifying type information in arginfo without fear of breaking
> things.
>
> Regards,
> Nikita
>

I'm all for it but what is the scope of the RFC?
Is it all core functions, bundled extension functions, or all extension
functions?
Also does this means that there will be argument type hinting in core
functions that
could be found out via reflection?

Best regards

George P. Banyard

--00000000000096f808058124ad3e--