Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114137
MIME-Version: 1.0
References: <V7C5-r6tzKmxjhPnvy9gtfdMtxkj0z_PJphaehaqcPsOLX0pEKtGU4A8EuSKyS-cbZl5HPVA2ejXCuXXOfOksH9VACGOKT3awRsr9aSNIg8=@protonmail.com>
 <5b9f1500-615a-48f1-815f-1d48b327ef90@processus.org> <CAJpLVh2UybGgAqhfAGQ=kKQ-qvmG68HWKaUJXOwPv7DgEbAdKw@mail.gmail.com>
 <179049b1475.11134368b213512.254739612773841999@void.tn> <CAJpLVh0pz_WopKza=XXqPrvS4bQZhWom1FQ6QLW-fbC-8JHkrA@mail.gmail.com>
In-Reply-To: <CAJpLVh0pz_WopKza=XXqPrvS4bQZhWom1FQ6QLW-fbC-8JHkrA@mail.gmail.com>
Date: Sat, 24 Apr 2021 21:51:50 +0200
Message-ID: <CADyq6sLtgNkyM-qQcwRY8mMOxnkrz_9qeG6XK2uDBqsh=smMtg@mail.gmail.com>
To: =?UTF-8?Q?Olle_H=C3=A4rstedt?= <olleharstedt@gmail.com>
Cc: Saif Eddin Gmati <azjezz@void.tn>, Pierre <pierre-php@processus.org>, 
	Saif Eddin Gmati <azjezz@protonmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000007211305c0bd3f78"
Subject: Re: [PHP-DEV] [RFC][Draft] Sealed Classes
From: ocramius@gmail.com (Marco Pivetta)

--00000000000007211305c0bd3f78
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, Apr 24, 2021, 21:44 Olle H=C3=A4rstedt <olleharstedt@gmail.com> wro=
te:

> 2021-04-24 17:59 GMT+02:00, Saif Eddin Gmati <azjezz@void.tn>:
> >> Doesn't this violate the principle: It should be possible to add new
> >> features without touching old code?
> >
> > This depends on which syntax is picked, both `for` and attribute syntax
> will
> > be completely BC.
>
> I'm not talking about BC, but the maintainability of the new feature
> itself. For the shape example, you'd need to edit the original file
> for each new shape you add, which is detrimental for maintainability
> and scalability. So what's a good use-case?
>

The main use-case of sealed types is being able to declare total functions
around them.

--00000000000007211305c0bd3f78--