Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104227
MIME-Version: 1.0
References: <CAF+90c9E6O-12fKKY_kb5b_LvXgODbPpC73TNro+XpMewndT2Q@mail.gmail.com>
 <CAOWwgpk0EsJB1t6XEGQYL9Zj2e5oTFXo2ijv7Pn7HMzB=oA88w@mail.gmail.com>
In-Reply-To: <CAOWwgpk0EsJB1t6XEGQYL9Zj2e5oTFXo2ijv7Pn7HMzB=oA88w@mail.gmail.com>
Date: Wed, 6 Feb 2019 09:18:25 +0100
Message-ID: <CAF+90c9xKmK1ozY29RwpVVMOnDcn3kY=M2m9Pjv5f2hqX8RGoQ@mail.gmail.com>
To: Nicolas Grekas <nicolas.grekas@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000cbcb770581355fda"
Subject: Re: [PHP-DEV] [RFC] Consistent type errors for internal functions
From: nikita.ppv@gmail.com (Nikita Popov)

--000000000000cbcb770581355fda
Content-Type: text/plain; charset="UTF-8"

On Wed, Feb 6, 2019 at 7:30 AM Nicolas Grekas <nicolas.grekas@gmail.com>
wrote:

> Hi Nikita
>
>
> https://wiki.php.net/rfc/consistent_type_errors
>
>
> Would it make sense and be possible to trigger a deprecation notice in PHP
> 7.4?
>
> That might help the ecosystem move forward in a smooth way instead of
> experimenting the failure when actually moving to 8.
>
> Nicolas
>

I don't think so. We generally consider a warning a "harder" error than a
deprecation (unlike deprecations, they are part of the default
error_reporting level), so I don't think replacing or adding a deprecation
would do much here. The only way you can be unaware of problems resulting
from this change is if you are deliberately suppressing warnings, in which
case chances are very good that you are also suppressing deprecations.

Nikita

--000000000000cbcb770581355fda--