On 15/03/2022 23:02, Patrick ALLAERT wrote:
This is not far from the reason why I voted "no".
I am not against the fact this warning becomes an error per se. I am just
not very fan of cherry-picking an individual kind of problem (read:
notice/warning/error/...) and changing it without a more
Am 16.03.2022 um 11:39 schrieb Mark Randall :
> On 16/03/2022 09:17, Christian Schneider wrote:
>> Maybe we should ask ourselves the question: Why would the entire package be
>> blocked? Just because it is too big or maybe there *are* subtleties which
>> have not been properly resolved?
>
>
On 16/03/2022 09:17, Christian Schneider wrote:
Maybe we should ask ourselves the question: Why would the entire package be
blocked? Just because it is too big or maybe there *are* subtleties which have
not been properly resolved?
It's politics and the practicalities of getting things done.
Am 16.03.2022 um 10:00 schrieb Mark Randall :
> On 15/03/2022 23:02, Patrick ALLAERT wrote:
>> I am not against the fact this warning becomes an error per se. I am just
>> not very fan of cherry-picking an individual kind of problem (read:
>> notice/warning/error/...) and changing it without a
On 15/03/2022 23:02, Patrick ALLAERT wrote:
I am not against the fact this warning becomes an error per se. I am just
not very fan of cherry-picking an individual kind of problem (read:
notice/warning/error/...) and changing it without a more global frame.
I think we should try to hit all of
Am 16.03.2022 um 06:52 schrieb Juliette Reinders Folmer
:
> I've just been looking in detail at the Partially Supported Callables
> deprecation RFC:
> https://wiki.php.net/rfc/deprecate_partially_supported_callables
>
> The RFC explicitly excludes the `is_callable()` function and the
Am 15.03.2022 um 20:07 schrieb Miguel Rosales :
> Christoph M. Becker wrote on 15/3/22 19:17:
>> That explicitly excludes undefined array indexes, and apparently also
>> excludes undefined properties (which raise "Warning: Undefined property:")
>>
> AFAIU error promotion for undefined properties
