Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120036
MIME-Version: 1.0
References: <8a9a04b3-45e6-47dd-dee8-0f524e49bd37@gmail.com>
 <CAOWwgpnPxDg0VWCtwn9ALAdiHNn1SFjLAsvVJiMaR-QQc0fU2A@mail.gmail.com>
 <CALKiJKrCXgWmBzWB_HfcqbrA8G4xLDzdryOkcy+JjUCWm4fC5Q@mail.gmail.com>
 <CAOWwgpmOFek0oZt9aOg44nCbcbcY7J3T-Ghw=UvFFd6Ugr=pRA@mail.gmail.com>
 <c17185c0-9bbb-43be-9127-6dfc5ea6e33d@gmail.com> <c694900b-5f0d-493f-a454-9d51acd09ac4@app.fastmail.com>
 <52a5a80d-f03f-5e96-4188-272a705e3fdd@gmail.com> <b366ccc1-cb3a-4f1d-9f90-dc7043cbb588@app.fastmail.com>
 <CAOWwgpmudjArTFMxUsYL_1SDT+yEQAYKRa-6MTUqOUxxi0sa=g@mail.gmail.com>
In-Reply-To: <CAOWwgpmudjArTFMxUsYL_1SDT+yEQAYKRa-6MTUqOUxxi0sa=g@mail.gmail.com>
Date: Fri, 14 Apr 2023 06:35:39 +0200
Message-ID: <CABdc3WoSgKnjE9gktLB4xzjiqg6X1+quMb3-G67xppkar3zBcQ@mail.gmail.com>
To: Nicolas Grekas <nicolas.grekas+php@gmail.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000003176cb05f9446048"
Subject: Re: [PHP-DEV] Brainstorming idea: inline syntax for lexical
 (captured) variables
From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Marcin_Brzuchalski?=)

--0000000000003176cb05f9446048
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Nicolas,

czw., 13 kwi 2023 o 14:40 Nicolas Grekas <nicolas.grekas+php@gmail.com>
napisa=C5=82(a):

> Hi Rowan, hi all!
>
> Le ven. 17 mars 2023 =C3=A0 15:51, Larry Garfield <larry@garfieldtech.com=
> a
> =C3=A9crit :
>
> > On Thu, Mar 16, 2023, at 6:05 PM, Rowan Tommins wrote:
> > > On 16/03/2023 22:14, Larry Garfield wrote:
> > >> Wouldn't the functionality described boil down to essentially just
> > materializing into a few extra lines in the constructor?  At least to m=
y
> > ignorant non-engine brain it seems straightforward to have this:
> > >>
> > >> $a =3D 1;
> > >> $b =3D 2;
> > >> $c =3D 3;
> > >>
> > >> $o =3D new class ($a, $b) use ($c) {
> > >>    public function __construct(private int $a, private int $b) {}
> > >>    public function something() {}
> > >> }
> > >>
> > >> Desugar to this:
> > >>
> > >> $c =3D class ($a, $b) use ($c) {
> > >>    private $c;
> > >>    public function __construct(private int $a, private int $b) {
> > >>      $this->c =3D 3;  // By value only, so this should be fine?
> > >>    }
> > >>    public function something() {}
> > >> }
>

Have you thought about not populating property by default but instead:
* adding "use" language construct as default to all methods?
* adding ability to assign variable values from "use" to property if needed=
?

Like desugar to
$c =3D class ($a, $b) use ($c) {
    private $c =3D $c; // optional, not required, no conflicts
    public function __construct(private int $a, private int $b) use ($c) {
        $this->c =3D $c % 2 ? 3 : 5;
    }
    public function something() use ($c) {
        return $c;
    }
}

Or there is something so wrong with this thinking I cannot see yet.

Cheers,
Micha=C5=82 Marcin Brzuchalski

--0000000000003176cb05f9446048--