Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110183
Return-Path: <marandall@php.net>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 16316 invoked from network); 16 May 2020 15:43:02 -0000
Received: from unknown (HELO localhost.localdomain) (76.75.200.58)
  by pb1.pair.com with SMTP; 16 May 2020 15:43:02 -0000
To: internals@lists.php.net
References: <CANZOY=AHs40Dzo_G44Q9byDbJ7emu5yDpmBMTSQ2uCXSARG_Dw@mail.gmail.com>
Date: Sat, 16 May 2020 15:20:43 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <CANZOY=AHs40Dzo_G44Q9byDbJ7emu5yDpmBMTSQ2uCXSARG_Dw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
X-Posted-By: 87.81.129.66
Subject: Re: [RFC] Strict operators directive
From: marandall@php.net (Mark Randall)
Message-ID: <php.internals-110183@news.php.net>

On 15/05/2020 23:03, Arnold Daniels wrote:
> Hi all,
> 
> I'd like to restart the discussion for the strict_opterators RFC (
> https://wiki.php.net/rfc/strict_operators).

I think this kind of change will have a long term positive impact, but 
it will require a lot of work to update code.

IMHO we need to know what is happening with editions, as I think this 
would be an ideal candidate for that rather than another declare

It would would give people <x> years warning that they've got that long 
to add their correct castings etc before the old behaviour is removed.