Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108572
MIME-Version: 1.0
References: <CAH5C8xWFBJ32XvnQGfwwuCw4-E2oFXgizSxzYuF0jk5Bt_xHWQ@mail.gmail.com>
In-Reply-To: <CAH5C8xWFBJ32XvnQGfwwuCw4-E2oFXgizSxzYuF0jk5Bt_xHWQ@mail.gmail.com>
Date: Fri, 14 Feb 2020 14:30:35 +0100
Message-ID: <CADyq6s+wnpMgQmLvsw1r_njCRj5t=sGg8wtpbKWDi1QqYa56PQ@mail.gmail.com>
To: =?UTF-8?B?TcOhdMOpIEtvY3Npcw==?= <kocsismate90@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000916ee9059e89361f"
Subject: Re: [PHP-DEV] [RFC] [PROPOSAL] Immutable/final/readonly properties
From: ocramius@gmail.com (Marco Pivetta)

--000000000000916ee9059e89361f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 14, 2020 at 2:23 PM M=C3=A1t=C3=A9 Kocsis <kocsismate90@gmail.c=
om> wrote:

>
> So far, my biggest question (apart from the name) have been how non-typed
> properties should behave: as they are implicitly initialized to null if
> they don't have an explicit default value (while typed properties remain
> uninitialized), further modifications would be impossible to do on them -
> which would make non-typed final properties almost useless. Nikita
> suggested to just avoid their initialization, but I'd be curious about
> other ideas as well.
>

Considering that PHP 8 will have union types, adding un-typed properties
support seems like a waste of time.

If somebody really wants a `mixed` property to be immutable, they could
write `private immutable null|bool|int|float|string|array|object
$property;`.

That would make implementation straightforward, since you'd expect
`immutable` to be before a type declaration (can be done in the parser,
right?).

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/

--000000000000916ee9059e89361f--