Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119203
MIME-Version: 1.0
References: <CAGtygW9ELxdusLyqgBvayMkB=dVRCUMCMY0ScS1qtX0Gr=-dWQ@mail.gmail.com>
 <CF506750-CA12-46A5-B92A-85EEF91E7331@gmail.com>
In-Reply-To: <CF506750-CA12-46A5-B92A-85EEF91E7331@gmail.com>
Date: Fri, 23 Dec 2022 12:10:59 +0100
Message-ID: <CANS-=pcg8ZmfJUF860FOV=HcAb931fBA0u86mNJA178ekTG6dw@mail.gmail.com>
To: Claude Pache <claude.pache@gmail.com>
Cc: joke2k <joke2k@gmail.com>, internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000be717a05f07cd809"
Subject: Re: [PHP-DEV] Methods which auto-return the class instance
From: kjarli@gmail.com (Lynn)

--000000000000be717a05f07cd809
Content-Type: text/plain; charset="UTF-8"

On Fri, Dec 23, 2022 at 10:33 AM Claude Pache <claude.pache@gmail.com>
wrote:

>
> ```php
> public function hit(): $this { $this->counter++; }
> ```
>
> Here, there is only one possible return value, and therefore the `return`
> instruction might be reasonably omitted.
>
> The real question is: Is it worth to add special cases for some specific
> return values?
>

We do have true, false, and null as return types (
https://www.php.net/releases/8.2/en.php#null_false_true_types). I'm
personally not opposed to having `$this` as return type, but it also starts
getting close to short function notations.

--000000000000be717a05f07cd809--