Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127434
Message-ID: <c5485d9c-e2de-4bf7-b192-ae6bc50ab58d@sandfox.me>
Date: Fri, 23 May 2025 04:53:54 +0300
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] RFC: Single-Expression functions
To: internals@lists.php.net
References: <CANTuiHuOxuwB2oTvPNekdkUCJbxWHMMrXjzQfHo2Tsui6NyoXw@mail.gmail.com>
Content-Language: en-US
In-Reply-To: <CANTuiHuOxuwB2oTvPNekdkUCJbxWHMMrXjzQfHo2Tsui6NyoXw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
From: sandfox@sandfox.me (Anton Smirnov)

Hi Dmitriy

On 22/05/2025 12:24, Dmitry Derepko wrote:
 > I'm aware that Larry Garfield previously proposed a similar feature
 > several years ago, though it unfortunately didn't pass the voting stage.
 > I would like to respectfully suggest that using "=" instead of "=>" to
 > separate declaration and implementation might be a better approach.
That looks like the weakest part of the proposition because we already 
have two places where inline bodies are used: the mentioned arrow 
functions and property hooks

   public string $foo { get => 'dynamic value'; }

No sense in introducing a new syntax for basically just another case of 
inline function body.

 > // oneline
 > function handle(string $input): string = func1($input) |> func2(...) 
|>            func3(...) |> func4(...);

That looks like a callable assignment like you know

   $f = fn ($bar) => $this->bar + $bar;

   class Foo {
       private $bar;

       public function bar() = $f;
   }

that may confuse users, another argument for =>

-- 
Anton