Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101910 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16551 invoked from network); 23 Feb 2018 14:42:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Feb 2018 14:42:13 -0000 Authentication-Results: pb1.pair.com header.from=me@kelunik.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=me@kelunik.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain kelunik.com from 81.169.146.219 cause and error) X-PHP-List-Original-Sender: me@kelunik.com X-Host-Fingerprint: 81.169.146.219 mo4-p00-ob.smtp.rzone.de Received: from [81.169.146.219] ([81.169.146.219:25737] helo=mo4-p00-ob.smtp.rzone.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A1/E5-01511-348209A5 for ; Fri, 23 Feb 2018 09:42:12 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1519396929; s=strato-dkim-0002; d=kelunik.com; h=Content-Type:Cc:To:Subject:Message-ID:Date:From:References: In-Reply-To:X-RZG-CLASS-ID:X-RZG-AUTH; bh=XK1bb2nqSa36j+yxT6FI7m3jvexsHV44R2NWe83isY4=; b=i+fVpHEYLeDKHH2Qh7NqUgI5iEvQ9KlLtKlAW8orADbQA4uk86pZrLJuevIyzoALx9 j+wG2FdZ3ohLJqpKpv/v3KDCCXkZB7qSJORT1L6aPoUz9ImHy+5yhrMJ2LrK5wIVmBc0 Ayb14+UE3kw4oNfIxNIMcZAYbjyq3j/tkSo1gGeS2aCcAsSjqb6XY1XDjpncfVbEAozr JiXafTaED25VaQgSODSsDe+qSknZXg5q05FMSqBc4onXWMPy9LPWR5ujRvzu1TE+FZae axlg6j88X0ajhfYNHw1fBLDhePUoRJxvD99dnFM+k5nqtkiJW5wk0pZ+Jx4XkzrMwwML qS6Q== X-RZG-AUTH: :IWkkfkWkbvHsXQGmRYmUo9mlsGbEv0XHBzMIJSS+jKTzde5mDb8AaBUcZiAlcA== X-RZG-CLASS-ID: mo00 Received: by mail-yb0-f179.google.com with SMTP id u8-v6so1226825ybo.10 for ; Fri, 23 Feb 2018 06:42:09 -0800 (PST) X-Gm-Message-State: APf1xPDe5XN19QZ8C6Rnec4W9Hlmn9kWtLyiaMqWwym5lNO4CVHPyyJB vp7X/0M2+I48nNtnk8g7GlJ8+xgLGMLen2etiP8= X-Google-Smtp-Source: AG47ELtzq6ox4V+ArohSAokXS6u5R7nY2I4RtECvbEP2xHGATfYymhXpHEFADJNz10I5Wse6EMYSVK5XlRtz0Mc28/8= X-Received: by 2002:a25:ed4:: with SMTP id 203-v6mr1202533ybo.448.1519396928335; Fri, 23 Feb 2018 06:42:08 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a25:a04a:0:0:0:0:0 with HTTP; Fri, 23 Feb 2018 06:42:07 -0800 (PST) In-Reply-To: <2B23EFFB-21C3-49E4-9000-B2E0F97E93A2@gmail.com> References: <2B23EFFB-21C3-49E4-9000-B2E0F97E93A2@gmail.com> Date: Fri, 23 Feb 2018 15:42:07 +0100 X-Gmail-Original-Message-ID: Message-ID: To: Paul Jones Cc: =?UTF-8?Q?Silvio_Mariji=C4=87?= , PHP Internals List Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV][RFC][DISCUSSION] Immutability From: me@kelunik.com (Niklas Keller) Hey, > If you do allow arrays, they would have to follow the same rules as the immutable object. > > Alternatively, perhaps an ImmutableArrayObject would be a good addition or followup to the RFC. That would just move the problem and doesn't have any benefit over directly allowing arrays, right? > Some further points to harden the implementation: > > - I see that resources and references are disallowed (which is good). If you have not already done so, you may wish to disallow streams as well. Streams are resources, am I missing something? Regards, Niklas