Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:97263
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAAn=CzVhq5YzW0FT44jSdmPsuk5z0ihk2qbEZhT4BP6QA_Sc3A@mail.gmail.com>
References: <CAAn=CzXJTy4e7sRtFiXM-RtY8iwx2xu3bDZTgy=Ge7dRUc6XdA@mail.gmail.com>
 <CAAn=CzXDAmJHhmYZ6p5g+6a-i7RnEk_COA0dze=d5gvBBrxeig@mail.gmail.com>
 <CAAn=CzXjy7OECAHO29vNfPrSGjrcQ1Dx1hCObHmXJskQ+zG9Tg@mail.gmail.com>
 <CAEsg9X1MvNUCWD4D46ibtfD2aJmj-uYjjj4Y1_Y5-fba1N1NTQ@mail.gmail.com>
 <CAAn=CzW7SQ_Oey76rzFMngMkcR3TCM7zjbp5AyP+Okorp+CWng@mail.gmail.com>
 <CAEsg9X3TJ=VWt9g6v8ZdoZ3220D=dh87XY392D2+mV1nDvtM8Q@mail.gmail.com>
 <CAAn=CzV8A3iytKLm7fECVcWoPZDutBUaJpe2qLUGThgz5DTTCA@mail.gmail.com> <CAAn=CzVhq5YzW0FT44jSdmPsuk5z0ihk2qbEZhT4BP6QA_Sc3A@mail.gmail.com>
Date: Fri, 2 Dec 2016 14:56:49 +0000
Message-ID: <CAAn=CzVD_CcdaRrg5v7dGd8iSX54UNoqSK6f-yf1RvppSCeoEg@mail.gmail.com>
To: PHP <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11441764d3365f0542ae25db
Subject: Fwd: [PHP-DEV] Re: [Concept] Magic Casting
From: bowersbros@gmail.com (Alex Bowers)

--001a11441764d3365f0542ae25db
Content-Type: text/plain; charset=UTF-8

Sorry for forward. Hit reply, not reply-all.

---------- Forwarded message ----------
From: Alex Bowers <bowersbros@gmail.com>
Date: 2 December 2016 at 14:31
Subject: Re: [PHP-DEV] Re: [Concept] Magic Casting
To: David Rodrigues <david.proweb@gmail.com>


Another benefit this would give frameworks / user land code is the ability
to mock / simulate having scalar object types.

For instance, A class called `Str` could be used to cast all "string"
inputs to its type, and then everywhere in the framework / user land code,
based on __cast() it could cast them all to a Str instance, and be used
with methods on.

This will allow

$string->toUpperCase() to be possible etc, whilst acting on a plain string.

On 2 December 2016 at 14:30, Alex Bowers <bowersbros@gmail.com> wrote:

> To me, in pseudo logic it would work as so:
>
> Currently it does this:
>
> A method with the signature of function_name(Collection $collection) has
> been called. The parameter I have is of type Collection. Let it continue;
> or alternatively, the parameter is not of type Collection, throw the error.
>
> The new method will be:
>
> A method with the signature of function_name(Collection $collection) has
> been called. The parameter I have is of type collection. let it continue.
>
> Alternatively,
> The parameter is not of type collection, does Collection implement a
> __cast() magic method. If it does, Pass the parameter into that __cast()
> method. If the response is an instance of Collection, let it through. If it
> is not, throw the error.
>
> As to how this would be implemented, r how the engine is built. This is
> not something I am aware of really. I will be willing to learn, and assist
> somebody / get assistance in the building of this feature, but it would
> take me a lot longer than it would take a real core member to do.
>
> But effectively, it will call Type::__cast()
>

--001a11441764d3365f0542ae25db--