Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71171
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <005001cf124f$3a40df00$aec29d00$@tutteli.ch>
References: <CABDNdAGCH5i9-=4Ys1CXeNaGWGmX=mkTiq0b7BbUKtBPdQ9XVg@mail.gmail.com>
	<001301cf1227$6d082ab0$47188010$@tutteli.ch>
	<CABDNdAHZTcE09kS-r_XTGOE9Q5EjTsEQyvzd29q0_nUqnPRrfQ@mail.gmail.com>
	<CAF9U7z-qR-JnXmbuS-ok2NnB_QzecM1Z4MGhek77rktdSYmcmQ@mail.gmail.com>
	<CADyq6s+KqD4Sp00NcJKDAAxX+xWT4x1C3_D1zMVqZ1PRKf__9w@mail.gmail.com>
	<002d01cf1234$01e6dc60$05b49520$@tutteli.ch>
	<CABDNdAEAQyyLQXFw3tw8S9Rb=+9Z-k1K_geX6HG7x1reCoJ5Rw@mail.gmail.com>
	<004c01cf123d$35730870$a0591950$@tutteli.ch>
	<52D71748.1090402@googlemail.com>
	<52D71FAE.8030002@ajf.me>
	<005001cf124f$3a40df00$aec29d00$@tutteli.ch>
Date: Thu, 16 Jan 2014 10:18:01 +0100
Message-ID: <CAEp07h_KDafvOMzxVmgQq1XMeO_N3CWdFCN0vVgdxXtEn6imKg@mail.gmail.com>
To: Robert Stoll <php@tutteli.ch>
Cc: Andrea Faulds <ajf@ajf.me>, Crypto Compress <cryptocompress@googlemail.com>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e013c6fa0ee598804f012e6d8
Subject: Re: [PHP-DEV] Introducing "Array Of" RFC
From: martin.keckeis1@gmail.com (Martin Keckeis)

--089e013c6fa0ee598804f012e6d8
Content-Type: text/plain; charset=UTF-8

2014/1/16 Robert Stoll <php@tutteli.ch>

>
>
> > -----Original Message-----
> > From: Andrea Faulds [mailto:ajf@ajf.me]
> > Sent: Thursday, January 16, 2014 12:54 AM
> > To: Crypto Compress; internals@lists.php.net
> > Subject: Re: [PHP-DEV] Introducing "Array Of" RFC
> >
> >
> >
> > On 15/01/14 23:18, Crypto Compress wrote:
> > > e.g.: function foo(Bar[null] = null)
> >
> > I'd prefer the ? syntax for nullables that C# has. I'm imagining
> > something like this:
> >
> > function foo(Bar? $a) {}   // $a is Bar/null
> > function foo(Bar?[] $a) {} // $a is array of Bars/nulls
> > function foo(Bar[]? $a) {} // $a is array of Bars, or null
> > function foo(Bar?[]? $a) {} // $a is array of Bars/nulls, or null
> >
> > --
> > Andrea Faulds
> > http://ajf.me/
> >
> > --
>
> I like Andrea's proposal, this way we can support all scenarios.
> It is possible to define that NULL is a valid entry in an array and we
> would stick to the same decision as for actual
> parameters, namely that one has to define explicitly that null is a valid
> entry. This would make me happy and I suppose
> also Philip.
>
> Just as side notice, this syntax would also give the chance for PHP to get
> rid of the double meaning of "=null" in a
> later version. I am talking about the following case:
> function foo(Foo $a=null, $b=1){}
> Where one might not want to specify that $a is optional but cannot do it
> differently at the moment - with the additional
> ? it could change :)
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
+ 1 for the RFC

But if i'm not completely wrong, there is performance decrease instead of
increase in your tests?
https://gist.github.com/krakjoe/8444591

[joe@fiji php-src]$ sapi/cli/php isTest.php 10000
objects: 10000
arrayof:        0.00645113
instanceof:     0.00560713

--089e013c6fa0ee598804f012e6d8--