Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72848 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 12577 invoked from network); 27 Feb 2014 22:28:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Feb 2014 22:28:22 -0000 Authentication-Results: pb1.pair.com header.from=larry@garfieldtech.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=larry@garfieldtech.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain garfieldtech.com from 66.111.4.27 cause and error) X-PHP-List-Original-Sender: larry@garfieldtech.com X-Host-Fingerprint: 66.111.4.27 out3-smtp.messagingengine.com Received: from [66.111.4.27] ([66.111.4.27:33136] helo=out3-smtp.messagingengine.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CD/A2-33117-50CBF035 for ; Thu, 27 Feb 2014 17:28:22 -0500 Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 8734B20F78 for ; Thu, 27 Feb 2014 17:28:19 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Thu, 27 Feb 2014 17:28:19 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=IlOkvTRz3oa9PgZNxffkm2 vtR2M=; b=DrBOkof2rFDueWUUKN6jcJq5B9N/z7FlMNP2ewGxZkuIrnk6o9wZXJ A0yP6iWuTbL/Y7oAWGob2VEbocFKsqbRpq102Ua5ml4DeS4dfJIaSH6HCCAJ01pF gWj64sz4sUv6muwkBI2KTZUfxB1vOv6xl6a48KwRR8dqYVXsgDKEY= X-Sasl-enc: LrRrzgmEOxOdCNHgUZZ2jaCcFN2xprmWxK764MbqOyPB 1393540099 Received: from Palantirs-MacBook-Pro-2.local (unknown [63.250.249.138]) by mail.messagingengine.com (Postfix) with ESMTPA id 4F74A6801A7 for ; Thu, 27 Feb 2014 17:28:19 -0500 (EST) Message-ID: <530FBC03.8020408@garfieldtech.com> Date: Thu, 27 Feb 2014 16:28:19 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: internals@lists.php.net References: <52D865C7.4070009@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Introducing "Array Of" RFC From: larry@garfieldtech.com (Larry Garfield) On 2/27/14 3:34 PM, Marco Pivetta wrote: > On 27 February 2014 22:11, Philip Sturgeon wrote: > >> So, should we allow nulls in an arrayof-style type hint? >> >> > `null` has its own type, which is mismatching the type required by the > array-of syntax when requesting, for example, `Foo[]`. > > If `null` was allowed in the array, as a user, I'd still be forced to > `array_filter()` on every call, so it would defeat the new feature > completely. ^^ My general stance. (Unless an "allow both" syntax is possible; if not, the above.) --Larry Garfield