Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108803
MIME-Version: 1.0
References: <3f615d82-a84b-697b-5c02-8d915270f92c@gmail.com> <CAAwdEzB6QjUnjWCh8-Tp9pr93gExgsHhw3s+N9xp+-QPuG7t7g@mail.gmail.com>
In-Reply-To: <CAAwdEzB6QjUnjWCh8-Tp9pr93gExgsHhw3s+N9xp+-QPuG7t7g@mail.gmail.com>
Date: Mon, 2 Mar 2020 14:08:24 +0000
Message-ID: <CALKiJKqYyVhKAV8nsmj66R0oAY-YH7n3crxNM6USX_jeakOE4A@mail.gmail.com>
To: =?UTF-8?Q?Alexandru_P=C4=83tr=C4=83nescu?= <drealecs@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Increment/Decrement Fixes
From: rowan.collins@gmail.com (Rowan Tommins)

Hi Alexandru,


On 2 March 2020 09:22:57 GMT+00:00, "Alexandru P=C4=83tr=C4=83nescu"
<drealecs@gmail.com> wrote:
>For point 1 and 2, both the old and new behavior is silent. Can we
>think of
>a safer way to migrate?

That's a very good question, and one I don't have a particularly good answe=
r to.

The problem with this kind of behaviour change is that there's no way
for PHP to know whether a particular piece of code has been changed to
expect the new behaviour or not, and therefore whether to raise a
deprecation notice. An opt-in notice on *all* usages could allow the
user to build up a list of places in their code to check, but they'd
still need to manually track which they'd already looked at, so I'm
not sure how useful it would be.

What I will look into is how well static analysis tools such as
PHPStan and Psalm could build a similar list, as I think that's
generally a more useful approach.

Regards,
--=20
Rowan Tommins
[IMSoP]