Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112122
MIME-Version: 1.0
References: <eb143f8b-b242-47bb-9858-e6150dd7aea4@www.fastmail.com>
In-Reply-To: <eb143f8b-b242-47bb-9858-e6150dd7aea4@www.fastmail.com>
Date: Mon, 26 Oct 2020 15:23:09 +0100
Message-ID: <CABdc3WomkCRkUL0yrMA=y=Nt+QUVH1W9mAz-wm_tB3mkg_woOw@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000021432b05b293ac93"
Subject: Re: [PHP-DEV] [RFC] Short-function syntax
From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Marcin_Brzuchalski?=)

--00000000000021432b05b293ac93
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Larry,

I'm wondering why we hadn't thought yet about reducing the need for $this
in this syntax.
Since arrow functions have an ability to capture variables defined in
parent scope why not
think of the same for class properties which will automatically reduce
short methods verbosity.

class X {
    public function __construct(private int $foo, private int $bar) {}
    public function getFoo(): int =3D> $foo;
    public function getBar(): int =3D> $bar;
}

And then going further why not removing =3D from arrow which indicated that
there is no return value for void functions:

class X {
    public function __construct(private int $foo, private int $bar) {}
    public function getFoo(): int =3D> $foo;
    public function setFoo(int $value): void > $foo =3D $value;
    public function getBar(): int =3D> $bar;
    public function setBar(int $value): void > $bar =3D $value;
}

The use of > instead of =3D> could if possible indicate the method being vo=
id
and reduce even more:

class X {
    public function __construct(private int $foo, private int $bar) {}
    public function getFoo(): int =3D> $foo;
    public function setFoo(int $value) > $foo =3D $value;
    public function getBar(): int =3D> $bar;
    public function setBar(int $value) > $bar =3D $value;
}

Would it be possible?

If not I think we should reanimate property accessors.

Just dropping my 50 cents.

Best regards,
Micha=C5=82 Marcin Brzuchalski

wt., 20 pa=C5=BA 2020 o 20:20 Larry Garfield <larry@garfieldtech.com> napis=
a=C5=82(a):

> A while back, Nikita mentioned that it should now be easy to offer an
> abbreviated syntax for functions that are just a single expression.  I
> decided to take a crack at it and it turns out he was right.  I thus offe=
r
> this RFC:
>
> https://wiki.php.net/rfc/short-functions
>
> Hopefully I made a decent enough case for it.  It's entirely a convenienc=
e
> factor, but I think for many OOP cases (getter methods and factored out
> operations) and functional cases (where functions should generally be a
> single expression conceptually) it does make the code nicer, more compact=
,
> and more readable.
>
> *dons flame retardant suit*
>
> --
>   Larry Garfield
>   larry@garfieldtech.com
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
>

--00000000000021432b05b293ac93--