Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112127
Message-ID: <FF0F9F19-F9AE-4DEA-BE3B-D9DA85FAB0A6@newclarity.net>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_50F0E227-4D8C-4512-9D73-1BC712C362A6"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Tue, 27 Oct 2020 02:35:49 -0400
In-Reply-To: <CABdc3WomkCRkUL0yrMA=y=Nt+QUVH1W9mAz-wm_tB3mkg_woOw@mail.gmail.com>
Cc: Larry Garfield <larry@garfieldtech.com>,
 =?utf-8?Q?Micha=C5=82_Marcin_Brzuchalski?= <michal.brzuchalski@gmail.com>
To: php internals <internals@lists.php.net>
References: <eb143f8b-b242-47bb-9858-e6150dd7aea4@www.fastmail.com>
 <CABdc3WomkCRkUL0yrMA=y=Nt+QUVH1W9mAz-wm_tB3mkg_woOw@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Short-function syntax
From: mike@newclarity.net (Mike Schinkel)

--Apple-Mail=_50F0E227-4D8C-4512-9D73-1BC712C362A6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Oct 26, 2020, at 10:23 AM, Micha=C5=82 Marcin Brzuchalski =
<michal.brzuchalski@gmail.com> wrote:
>=20
> Hi Larry,
>=20
> 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.
>=20
> class X {
>    public function __construct(private int $foo, private int $bar) {}
>    public function getFoo(): int =3D> $foo;
>    public function getBar(): int =3D> $bar;
> }
>=20
> And then going further why not removing =3D from arrow which indicated =
that
> there is no return value for void functions:
>=20
> 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;
> }
>=20
> The use of > instead of =3D> could if possible indicate the method =
being void
> and reduce even more:
>=20
> 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;
> }
>=20
> Would it be possible?
>=20
> If not I think we should reanimate property accessors.

Which brings us back to https://externals.io/message/64469 =
<https://externals.io/message/64469> from 7 years ago.  And there is =
this: =
https://www.reddit.com/r/PHP/comments/budr7q/php_74_setters_and_getters_ha=
ve_died/ =
<https://www.reddit.com/r/PHP/comments/budr7q/php_74_setters_and_getters_h=
ave_died/>

With getters/setters, it would seem Larry's proposal might allow for =
more conciseness than it can with all other current syntax being the =
same as PHP 8.0 per Nikita.=20

Consider this, as one straw man type of new syntax:

class TimePeriod {
	private int $Seconds =3D 3600;
	public float $Hours {
		get():float =3D> $this->Seconds / 3600;
		set(int $v) =3D> $this->Seconds =3D intval($v*3600);
	}
}

Or for a different use-case with different straw man syntax that could =
possibly work in addition to above syntax, where externally $Balance is =
readonly whereas internally Balance is treated like it is private so it =
can be set (I also used Michal's ">" to indicate void, although I am not =
sure that using a greater-than in a different context is a good idea):

class Account {
	public get int $Balance;
	public function Deposit(int $amount) > $this->Balance +=3D =
$amount;
	public function Withdraw(int $amount) > $this->Balance -=3D =
$amount;
}


-Mike

>=20
> Just dropping my 50 cents.
>=20
> Best regards,
> Micha=C5=82 Marcin Brzuchalski


--Apple-Mail=_50F0E227-4D8C-4512-9D73-1BC712C362A6--