Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117353
MIME-Version: 1.0
References: <QHsa8Y5m94yZnEjyPcsmW3_G5d5GRZ3yRDFECWeUSgZ-uEb4almbDLic4beARbjYUUqCORy15oI1RQp4ePyE6H3J4t4Jqd9XtbSg2FKC0Dg=@protonmail.com>
In-Reply-To: <QHsa8Y5m94yZnEjyPcsmW3_G5d5GRZ3yRDFECWeUSgZ-uEb4almbDLic4beARbjYUUqCORy15oI1RQp4ePyE6H3J4t4Jqd9XtbSg2FKC0Dg=@protonmail.com>
Date: Thu, 17 Mar 2022 11:38:23 +0100
Message-ID: <CAOWwgpmzbA5F084kxGQ5v6JSuD_RMQMy9+kPgTLKm_TPc9vRqA@mail.gmail.com>
To: Saif Eddin Gmati <azjezz@protonmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000dba5fa05da67a1a4"
Subject: Re: [PHP-DEV] [RFC] [VOTE] Sealed Classes
From: nicolas.grekas+php@gmail.com (Nicolas Grekas)

--000000000000dba5fa05da67a1a4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Le jeu. 17 mars 2022 =C3=A0 04:54, Saif Eddin Gmati <azjezz@protonmail.com>=
 a
=C3=A9crit :

> Hello Internals,
>
> As per my last email in the previous thread, i have started the vote for
> sealed classes feature.
>
> The vote will run for 2 weeks until March 31st 2022.
>
> Discussion: https://externals.io/message/117173
>
> Draft Discussion: https://externals.io/message/114116
>
> RFC: https://wiki.php.net/rfc/sealed_classes
>

Hello Saif,

Thanks for the RFC.

I voted "no" because to me this closes extensibility in a hard way. If
users are fine ignoring an "@internal" annotation, or using reflection to
access private symbols, then I think that's fine: their problem; they know
why they need to do so - not authors. Allowing authors to forcibly remove
that capability from users is going too deep into removing power from users=
.

Said another way, I don't think this solves any problem that authors face
in practice. As such I don't think this is worth the added language
complexity + removal of power.

Cheers,
Nicolas

--000000000000dba5fa05da67a1a4--