Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104446
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: Sat, 16 Feb 2019 12:14:45 +0100
Message-ID: <CAF+90c-rxf4gXxRk+doGHFtLAkEuHw_87DLm0oo1xXTtr6WJRA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000c2b06c0582010070"
Subject: Re: [RFC] Consistent type errors for internal functions
From: nikita.ppv@gmail.com (Nikita Popov)

--000000000000c2b06c0582010070
Content-Type: text/plain; charset="UTF-8"

On Tue, Feb 5, 2019 at 12:22 PM 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
>

Heads up: This is headed for voting on Tuesday, assuming no significant
issues are raised in the meantime.

Nikita

--000000000000c2b06c0582010070--