Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116024
MIME-Version: 1.0
References: <CAF+90c9Qxuq=Q3eGq2pLHtvTP=z4pCTgtjwHOehTuOi4vZXvoA@mail.gmail.com>
 <75e31735-f082-5b05-1df3-40f14e0e9351@php.net>
In-Reply-To: <75e31735-f082-5b05-1df3-40f14e0e9351@php.net>
Date: Thu, 9 Sep 2021 11:26:20 -0300
Message-ID: <CAAwFBqpL9k0fuDiZFnndt=xEu+0a+J+PNgnPR3aDoajjiZFnUQ@mail.gmail.com>
To: Sebastian Bergmann <sebastian@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000000a350805cb90c9d4"
Subject: Re: [PHP-DEV] [RFC] $this return type
From: flaviohbatista@gmail.com (=?UTF-8?Q?Fl=C3=A1vio_Heleno?=)

--0000000000000a350805cb90c9d4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Sep 7, 2021 at 10:27 AM Sebastian Bergmann <sebastian@php.net>
wrote:

> Am 07.09.2021 um 12:28 schrieb Nikita Popov:
> > I have some reservations about this (which basically come down to $this
> not
> > being a proper "type", so should it be in the type system?) but I can s=
ee
> > the practical usefulness, so I think it's worth discussing this.
>
> I am not conviced that there is enough value in this to introduce syntax
> for it, but if at all, then please not "$this" as the name for a type.
>
> Off the top of my head, I think that "same" could make sense.
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
>
Hi all,

I'm sorry if I'm being naive, or simply put dumb, but the main difference
that we're trying
to achieve with having "$this" (or variations of it) as a valid return type
as opposed to simply
using "self" is to ensure that the underlying code is actually doing a
"return $this" rather
than returning any other valid "self" instance (such as "return new
self();")?

--=20
Atenciosamente,

    Fl=C3=A1vio Heleno

--0000000000000a350805cb90c9d4--