Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108575
MIME-Version: 1.0
References: <CAH5C8xWFBJ32XvnQGfwwuCw4-E2oFXgizSxzYuF0jk5Bt_xHWQ@mail.gmail.com>
 <CADyq6s+wnpMgQmLvsw1r_njCRj5t=sGg8wtpbKWDi1QqYa56PQ@mail.gmail.com>
In-Reply-To: <CADyq6s+wnpMgQmLvsw1r_njCRj5t=sGg8wtpbKWDi1QqYa56PQ@mail.gmail.com>
Date: Fri, 14 Feb 2020 14:42:44 +0100
Message-ID: <CAH5C8xVRuSz=CSi6okRPXmjQ+B25Hjp1QNwYgkXFJMHnpdbSGA@mail.gmail.com>
To: Marco Pivetta <ocramius@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000005641e059e8962b3"
Subject: Re: [PHP-DEV] [RFC] [PROPOSAL] Immutable/final/readonly properties
From: kocsismate90@gmail.com (=?UTF-8?B?TcOhdMOpIEtvY3Npcw==?=)

--00000000000005641e059e8962b3
Content-Type: text/plain; charset="UTF-8"

>
> If somebody really wants a `mixed` property to be immutable, they could
> write `private immutable null|bool|int|float|string|array|object
> $property;`.
>

Yeah, one of my ideas was to first add support for mixed (for which there
have been a proposal/PR since quite some time), so that all non-typed
properties
could be implicitly upgraded to the mixed type. But I don't think it's the
way to go... Maybe only if our long-term goal would be to deprecate/remove
non-typed properties and implicit initialization altogether in favour of
mixed type and implicit uninitialization...


> That would make implementation straightforward, since you'd expect
> `immutable` to be before a type declaration (can be done in the parser,
> right?).
>

Yeah, the implementation didn't seem very tricky yet (but people with more
experience with the internals of PHP should tell). However, Nikita also
warned me
not to support references. So this is another question to decide...

--00000000000005641e059e8962b3--