Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104230
MIME-Version: 1.0
References: <CAF+90c9E6O-12fKKY_kb5b_LvXgODbPpC73TNro+XpMewndT2Q@mail.gmail.com>
 <CAOWwgpk0EsJB1t6XEGQYL9Zj2e5oTFXo2ijv7Pn7HMzB=oA88w@mail.gmail.com> <CAF+90c9xKmK1ozY29RwpVVMOnDcn3kY=M2m9Pjv5f2hqX8RGoQ@mail.gmail.com>
In-Reply-To: <CAF+90c9xKmK1ozY29RwpVVMOnDcn3kY=M2m9Pjv5f2hqX8RGoQ@mail.gmail.com>
Date: Wed, 6 Feb 2019 09:43:02 +0100
Message-ID: <CAOWwgpke6okcmqeeUcq1ScTfnxXKwzB87ZdNJ7TzdOfYXfSXnA@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000693881058135b73e"
Subject: Re: [PHP-DEV] [RFC] Consistent type errors for internal functions
From: nicolas.grekas@gmail.com (Nicolas Grekas)

--000000000000693881058135b73e
Content-Type: text/plain; charset="UTF-8"

> 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.
>>
>
> We generally consider a warning a "harder" error than a deprecation
>

Do all situations that will throw after the RFC trigger a warning right
now? Eg var_dump(substr(null, 1)); doesn't trigger anything but returns
false - does that mean it will not throw a TypeError in your proposal?


> if you are deliberately suppressing warnings, in which case chances are
> very good that you are also suppressing deprecations.
>

This assumption is wrong in the Symfony ecoystem!
We built the deprecation framework around silenced (and unsilenced)
deprecations, which are all caught and logged.
So it would make a huge difference actually, at least for situations where
no warning is triggered (see substr example above).

Nicolas

--000000000000693881058135b73e--