Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120205
MIME-Version: 1.0
References: <CAJpLVh2qBgkn1VwaXt3yhWPM+W_SCc77j05L_DtmsHcVXhPeLg@mail.gmail.com>
In-Reply-To: <CAJpLVh2qBgkn1VwaXt3yhWPM+W_SCc77j05L_DtmsHcVXhPeLg@mail.gmail.com>
Date: Sat, 6 May 2023 19:45:20 +0300
Message-ID: <CABJDihvLmJQwy8SZ2jkRX70qLm8oCkQVqYqiHEpF2BA1Pc=Mow@mail.gmail.com>
To: =?UTF-8?Q?Olle_H=C3=A4rstedt?= <olleharstedt@gmail.com>
Cc: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000003dc4ce05fb092271"
Subject: Re: [PHP-DEV] Limit write access to object function parameters
From: lokrain@gmail.com (Lokrain)

--0000000000003dc4ce05fb092271
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hey there,

Looking at how to achieve =E2=80=9Creadonly input object=E2=80=9D now a few=
 things come in
my mind:
 * Write a readonly class in first place, assuming it=E2=80=99s not a class=
 from a
package you cannot or don=E2=80=99t want to update
 * Clone the object
 * Use a new immutable DTO for data transfer
 * Use stateless =E2=80=9Cservices=E2=80=9D (DI-ed)
 * Use static code analysers
 * Have conversations in your team

Having this in mind, such feature looks more or less as syntax sugar with
not much value. Nevertheless, I like it :)

Hope to see other comments.

Regards,
Dimitar




On Sat, 6 May 2023 at 13:55, Olle H=C3=A4rstedt <olleharstedt@gmail.com> wr=
ote:

> Heyo internalitos,
>
> I was thinking of having the possibility to use `readonly` (or any
> other keyword) to make a function argument behave as if it was a
> readonly object.
>
>     class Point
>     {
>       public int $x;
>       public int $y;
>     }
>     function doThing(readonly Point $p)
>     {
>       $p->x =3D 10;  // Not allowed
>     }
>
> In C# it's called in/out/ref types:
> https://www.pluralsight.com/guides/csharp-in-out-ref-parameters
>
> The main use-case is to not give away more access than you have to,
> and being able to state your intent in the function signature.
>
> Another alternative would be to allow properties in interfaces, and
> then define a readonly-like interface:
>
>     interface ReadonlyPoint
>     {
>       public readonly int $x;
>       public readonly int $y;
>     }
>     function doThing(ReadonlyPoint $p)
>     {
>       $p->x =3D 10;  // Not allowed
>     }
>
> No idea about practical feasability.
>
> Since arrays are value types, they're not really relevant for this
> suggestion. Same goes for string, int, etc.
>
> Regards
> Olle
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
>

--0000000000003dc4ce05fb092271--