Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119211
MIME-Version: 1.0
References: <CAGtygW9ELxdusLyqgBvayMkB=dVRCUMCMY0ScS1qtX0Gr=-dWQ@mail.gmail.com>
 <CF506750-CA12-46A5-B92A-85EEF91E7331@gmail.com> <CAGtygW_n-8cd24G6y7ffsV6TZ8KJ63x2LFGGknEOOU0Hu3oBdw@mail.gmail.com>
In-Reply-To: <CAGtygW_n-8cd24G6y7ffsV6TZ8KJ63x2LFGGknEOOU0Hu3oBdw@mail.gmail.com>
Date: Wed, 28 Dec 2022 13:53:57 +0700
Message-ID: <CAEZPtU4+DSvZjj+yd7SzGfYCPRWk6rLnY8GFYxGsYSp-XDNMOw@mail.gmail.com>
To: joke2k <joke2k@gmail.com>
Cc: Claude Pache <claude.pache@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000d5801005f0ddd550"
Subject: Re: [PHP-DEV] Methods which auto-return the class instance
From: pierre.php@gmail.com (Pierre Joye)

--000000000000d5801005f0ddd550
Content-Type: text/plain; charset="UTF-8"

On Fri, Dec 23, 2022, 7:46 PM joke2k <joke2k@gmail.com> wrote:

> Thanks for the feedback!
>
> On Fri, 23 Dec 2022, 09:33 Claude Pache, <claude.pache@gmail.com> wrote:
>
> > It is very common for fluent class methods to have a verbose `return
> > $this;` ending in their body.
> > But If you have declared `self` as return type into a non-static class
> > method you have only two options to return:
> >
> > - the $this object
> > - another instance of the same class or subclass
> >
> > ... in order to avoid a return type error.
> >
> >
> > It is still two options, and it is not clear in general which one to
> pick.
> > You could also say that, if you have `object` as return type, there are
> two
> > options to avoid a return type error: either return the `$this` object,
> or
> > return another object.
> >
>
> Yes but declaring `self` is more strict than `object`.
> And talking about the word itself... Declaring to return (your-)`self` but
> you could return someone-else of the same type as you.
> But it is ok, it refers to the class name not the instance. just semantic.
>

I would rather endure it returns the used instance and not another one with
a compatible interface. Not doing do is actually confusing to me, as per
the meaning of self. .

Or maybe, if the goal is to ease declaration of fluent interfaces (methods
chaining), declaring a class fluent (annotation?) would achieve the same
with ambiguous names?

>

--000000000000d5801005f0ddd550--