Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130058
Message-ID: <cabfee8c-92e6-401b-8a31-b92025dda315@gmail.com>
Date: Sun, 8 Feb 2026 22:40:38 +0700
Precedence: list
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] [RFC] Pipe to return
To: =?UTF-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>
Cc: internals@lists.php.net
References: <53c17181-caa4-41a3-b4ab-93069e6bb47b@gmail.com>
 <7351ad2ea062a074a94454257a241049@bastelstu.be>
Content-Language: en-US
In-Reply-To: <7351ad2ea062a074a94454257a241049@bastelstu.be>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
From: vadim.dvorovenko@gmail.com (Vadim Dvorovenko)

03.02.2026 22:13, Tim Düsterhus:

> While it is true that no one is forced to use the new syntax, I will 
> inevitably come across it in libraries that decide to use it, thus I 
> will be forced to know that it is a thing and to understand what it 
> does. And of course all IDEs and static analyzers will need to learn 
> about it as well. 
Of course, I can't cover all areas, especially proprietary IDEs. 
However, I planned to prepare corresponding changes for the following 
tools: nikic/PHP-Parser, psalm, phpstan, php-cs-fixer. If this could 
affect the vote, I can prepare changes to the this projects before the vote.