Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126029
Feedback-ID: ifab94697:Fastmail
Precedence: bulk
MIME-Version: 1.0
Date: Fri, 22 Nov 2024 00:07:35 +0100
To: internals@lists.php.net
Message-ID: <05db7ff5-0e80-4c5c-ac96-445053533ecb@app.fastmail.com>
In-Reply-To: <68eba37e-1bfe-4509-af41-112bb196415c@app.fastmail.com>
References: <d603f372-5f58-4308-aba1-151c35f3aa94@app.fastmail.com>
 <68eba37e-1bfe-4509-af41-112bb196415c@app.fastmail.com>
Subject: Re: [PHP-DEV] RFC: Records
Content-Type: multipart/alternative;
 boundary=ede335cfa57f4f01952173c7437da583
From: rob@bottled.codes ("Rob Landers")

--ede335cfa57f4f01952173c7437da583
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Sun, Nov 17, 2024, at 08:21, Larry Garfield wrote:
> I would far prefer assembling record-ish behavior myself, using the sm=
aller parts above.  Eg:
>=20
> final readonly data class Point(int $x, int $y);
>=20
> "final" prevents extension.  "readonly" makes it immutable.  "data" gi=
ves it value-passing semantics.  Any class can use an inline constructor=
.  "with" is designed to work automatically on all objects.  Boom, I've =
just assembled a Record out of its constituent parts, which also makes i=
t easier for others to learn what I'm doing, because the features opted-=
in to are explicit, not implicit.

Sorry for the radio silence, but I found myself saying something was imp=
ossible. This is software, anything is possible...

Anyway, I think I figured out how to implement a "data" modifier, and it=
 is quite excellent (for the exact reasons you give).

I'll break this up into multiple RFCs, pending some further tests to try=
 and break my proof-of-concept:

- a "data" modifier on class for value semantics
- an "inline constructor"

As you mention, at that point, a "record" or "value" keyword can just be=
 shorthand for "final readonly data class".

=E2=80=94 Rob
--ede335cfa57f4f01952173c7437da583
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Sun, Nov 17,=
 2024, at 08:21, Larry Garfield wrote:<br></div><blockquote type=3D"cite=
" id=3D"qt" style=3D""><div>I would far prefer assembling record-ish beh=
avior myself, using the smaller parts above.&nbsp; Eg:<br></div><div><br=
></div><div>final readonly data class Point(int $x, int $y);<br></div><d=
iv><br></div><div>"final" prevents extension.&nbsp; "readonly" makes it =
immutable.&nbsp; "data" gives it value-passing semantics.&nbsp; Any clas=
s can use an inline constructor.&nbsp; "with" is designed to work automa=
tically on all objects.&nbsp; Boom, I've just assembled a Record out of =
its constituent parts, which also makes it easier for others to learn wh=
at I'm doing, because the features opted-in to are explicit, not implici=
t.<br></div></blockquote><div><br></div><div>Sorry for the radio silence=
, but I found myself saying something was impossible. This is software, =
anything is possible...<br></div><div><br></div><div>Anyway, I think I f=
igured out how to implement a "data" modifier, and it is quite excellent=
 (for the exact reasons you give).<br></div><div><br></div><div>I'll bre=
ak this up into multiple RFCs, pending some further tests to try and bre=
ak my proof-of-concept:<br></div><div><br></div><div>- a "data" modifier=
 on class for value semantics<br></div><div>- an "inline constructor"<br=
></div><div><br></div><div>As you mention, at that point, a "record" or =
"value" keyword can just be shorthand for "final readonly data class".<b=
r></div><div><br></div><div id=3D"sig121229152">=E2=80=94 Rob<br></div><=
/body></html>
--ede335cfa57f4f01952173c7437da583--