Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89249
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.41 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <CABHuAWzi5n_5k_7QNLQNwYuD+xxWN9OcJsz28ED4OB=MVZuLCQ@mail.gmail.com>
References: <CABHuAWzi5n_5k_7QNLQNwYuD+xxWN9OcJsz28ED4OB=MVZuLCQ@mail.gmail.com>
Date: Mon, 16 Nov 2015 16:39:57 -0700
Message-ID: <CAFMT4Noxrof6f7gt7561RgLUhCD-bgYsgai4+s7-98TxSy5-MQ@mail.gmail.com>
To: Chris Riley <t.carnage@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a114268dc4f61400524b0ed83
Subject: Re: [PHP-DEV] Immutable modifier
From: levim@php.net (Levi Morrison)

--001a114268dc4f61400524b0ed83
Content-Type: text/plain; charset=UTF-8

On Mon, Nov 16, 2015 at 2:15 AM, Chris Riley <t.carnage@gmail.com> wrote:

> Hi,
>
> There has been a lot of interest recently (eg psr-7) in immutable data. I'm
> considering putting an RFC together to add language support for immutables:
>
> immutable class Foo {
> public $bar;
> public function __construct($bar) {
> $this->bar = $bar;
> }
> }
>
> Immutable on a class declaration makes all (maybe only public?) properties
> of the class immutable after construct; assigning to a property would
> result in a Fatal error.
>
> class Foo {
> public $bar;
> immutable public $baz;
> }
>
> Immutable on a property makes the property immutable once it takes on a
> none null value. Attempts to modify the property after this results in a
> fatal error.
>
> Any thoughts?
> ~C
>

In my opinion we should just generalize const for this, rather than add a
new keyword.

--001a114268dc4f61400524b0ed83--