Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130144
Precedence: list
MIME-Version: 1.0
References: <CE12E852-00AA-41E1-8E8A-B82B89F801A4@wcflabs.de>
In-Reply-To: <CE12E852-00AA-41E1-8E8A-B82B89F801A4@wcflabs.de>
Date: Mon, 23 Feb 2026 21:58:15 +0000
Message-ID: <CAGBsUrdczien7yCvQLNMQXOcJnZbmjOgAMQi4rD8uRxzkVsm8Q@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Readonly Variables
To: =?UTF-8?Q?Joshua_R=C3=BCsweg?= <josh@wcflabs.de>
Cc: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: tekiela246@gmail.com (Kamil Tekiela)

On Mon, 23 Feb 2026 at 21:29, Joshua R=C3=BCsweg <josh@wcflabs.de> wrote:
>
> Hi internals,
>
> I'd like to propose a new language feature for PHP: Readonly Variables.
>
> PHP currently has no way to declare a variable as immutable within a loca=
l or functional scope. This RFC proposes the readonly modifier for variable=
s, which prevents reassignment after the initial declaration and results in=
 an error on any attempt to do so.
>
> Key behaviors:
> - Reassignment and compound assignment operators are forbidden
> - Pass-by-reference is forbidden
> - unset() removes the readonly flag, allowing re-declaration
> - Readonly variables inside loops are permitted but limited to a single d=
eclaration
> - Scoping follows regular variable rules (function, method, closure bound=
aries)
>
> The RFC is available at:
> https://wiki.php.net/rfc/readonly-variables
>
> I'm looking forward to your feedback and discussion.
>
> Cheers,
> Joshua R=C3=BCsweg

Hi Joshua,

This is a very interesting proposal, but I feel like you haven't
explained all your choices. I have some questions:

1. Why the use of readonly keyword? Why not const or some new keyword,
e.g. locked.
2. Why does unset not remove the variable completely? If you want a
feature to only unlock the variable then it probably needs a new
keyword, e.g. unlock
3. What exactly does this mean: "Readonly variables inside loops are
permitted but limited to a single declaration"? What does a single
declaration look like?
4. How will this impact optimizer and JIT?
5. You said that readonly variables cannot be used with the global
keyword. But what about readonly variables in global scope? Will they
still behave like a typical global variable?
6. What exactly counts as a variable declaration? When is it a valid
syntax to use this keyword? I don't think PHP had the concept of
variable declaration until now.
7. What about compound variables such as arrays and objects?

I would prefer starting with readonly parameters as I feel that would
bring the most value.
I think it would also be worthwhile to investigate a simpler syntax
for define().

Regards,
Kamil