Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115991
MIME-Version: 1.0
References: <CAF+90c9Qxuq=Q3eGq2pLHtvTP=z4pCTgtjwHOehTuOi4vZXvoA@mail.gmail.com>
In-Reply-To: <CAF+90c9Qxuq=Q3eGq2pLHtvTP=z4pCTgtjwHOehTuOi4vZXvoA@mail.gmail.com>
Date: Tue, 7 Sep 2021 13:38:40 +0200
Message-ID: <CABdc3WqR-s6YxyBZYWTwtRs4FTcFamHhuC-UxyFZwHzyGcbmaw@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000b1af0605cb66358d"
Subject: Re: [PHP-DEV] [RFC] $this return type
From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Marcin_Brzuchalski?=)

--000000000000b1af0605cb66358d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Nikita,

wt., 7 wrz 2021 o 12:29 Nikita Popov <nikita.ppv@gmail.com> napisa=C5=82(a)=
:

> Hi internals,
>
> I'd like to pick up a loose thread from the future scope of the
> https://wiki.php.net/rfc/static_return_type RFC, the $this return type fo=
r
> fluent APIs:
>
> https://wiki.php.net/rfc/this_return_type
>
> I have some reservations about this (which basically come down to $this n=
ot
> being a proper "type", so should it be in the type system?) but I can see
> the practical usefulness, so I think it's worth discussing this.


If the aim of $this return type is to force and check the return $this why
would we still need/require return statement to be obligatory?
Does that make sense to assume at the end of function flow the return
$this; statement to be present by default if the return type is not an
union etc.?

Cheers,
--
Micha=C5=82 Marcin Brzuchalski

--000000000000b1af0605cb66358d--