Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105442
MIME-Version: 1.0
References: <DB6PR0701MB3048010E7D55F49CEAB98927E2590@DB6PR0701MB3048.eurprd07.prod.outlook.com>
In-Reply-To: <DB6PR0701MB3048010E7D55F49CEAB98927E2590@DB6PR0701MB3048.eurprd07.prod.outlook.com>
Date: Thu, 25 Apr 2019 11:51:43 +0200
Message-ID: <CAF+90c9X34yHpHO5aTYZ0-KJLRWQnNkbf_me=f_GyX61jVnghA@mail.gmail.com>
To: Bob Weinand <bobwei9@hotmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000000c9aa1058757c5d6"
Subject: Re: [PHP-DEV] [RFC] Change the precedence of the concatenation operator
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000000c9aa1058757c5d6
Content-Type: text/plain; charset="UTF-8"

On Thu, Mar 28, 2019 at 2:33 PM Bob Weinand <bobwei9@hotmail.com> wrote:

> Hey,
>
> I feel like concatenation having the same precedence than addition and
> subtraction is promoting programmers to make mistakes. Albeit typically
> easy to catch ones, it is a quality of life change at least.
>
> Hence I'm proposing a RFC changing the precedences:
> https://wiki.php.net/rfc/concatenation_precedence
>
> Bob
>

Similarly to the ternary associativity RFC, I've analyzed the top 2000
composer packages and checked whether they would be affected by this
change: https://gist.github.com/nikic/a4df3e8e18c7955c2c21cf6cdb4cbfaa

The tl;dr is that there were 5 instances where behavior would change per
this RFC, and all 5 of them are bugs in current code and would be
interpreted correctly after this RFC.

Nikita

--0000000000000c9aa1058757c5d6--