Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113966
To: PHP Internals <internals@lists.php.net>
References: <0b8301d72a3a$71045ca0$530d15e0$@webkr.de>
Message-ID: <6ba3d305-7eb8-24ce-2d58-a31154968724@gmail.com>
Date: Mon, 5 Apr 2021 13:26:52 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0)
 Gecko/20100101 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <0b8301d72a3a$71045ca0$530d15e0$@webkr.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Raising the precedence of the new operator
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

On 4/5/21 9:40 AM, André Hänsel wrote:
> I was wondering... PHP is the only language I know of where you have to
> write `(new Foo())->bar()` instead of
> `new Foo()->bar()`. This is particularly apparent with the builder pattern:

Enabling something that is syntax error now sounds pretty innocent, but 
I wonder if messing with precedence would cause some deeper consequences 
in different expressions. We need to be careful here given how much code 
(and how much weird code) there exists in PHP. If we can guarantee that 
we can enable this construct without causing any side effects, then it's 
fine I think.
-- 
Stas Malyshev
smalyshev@gmail.com