Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90345
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <568F0FB8.9030807@dasprids.de>
References: <CAFKaYMoZeOZSfhxesffNsmzdxXoPUAU86hpy3h6OGZL5_8+k7A@mail.gmail.com>
	<5605BACE.30803@gmail.com>
	<CAFKaYMr8D3pvNfoBmDkioy+kR4gVzOWD6Q7ZnoVphMhS=8DSWQ@mail.gmail.com>
	<5605C23D.6030104@gmail.com>
	<CAB6YZuzFO8cQFQ00AZbyrVaMEkamk6wTzbRxYB8Yr-7s9wHcFg@mail.gmail.com>
	<56065071.2070107@gmail.com>
	<CAFKaYMp6y_qkHmA7otBnCLOpJbMJNWgPghPq4PQfzZ5VAKszSQ@mail.gmail.com>
	<568F0FB8.9030807@dasprids.de>
Date: Thu, 7 Jan 2016 22:14:12 -0700
Message-ID: <CAObuZdviG+P5Zs-=DJnEgvPNV7Txa6php=7tVpgzMBBJS4PPHA@mail.gmail.com>
To: "Ben Scholzen 'DASPRiD'" <mail@dasprids.de>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e014935f46c84e60528cba8cb
Subject: Re: [PHP-DEV] Implementing Generics, and none scalar default properties.
From: derokorian@gmail.com (Ryan Pallas)

--089e014935f46c84e60528cba8cb
Content-Type: text/plain; charset=UTF-8

Hi Ben and Rasmus,

On Thu, Jan 7, 2016 at 6:24 PM, Ben Scholzen 'DASPRiD' <mail@dasprids.de>
wrote:

> By the way, Rasmus updated the RFC quite a bit, you guys may want to take
> a look at it again.
>
>
I just have a couple questions about the rfc, but overall I think its great
and I really hope it makes it into PHP!

Note that the choice of the keyword is to indicate upper bounds is based on
> the rejection of perhaps more obvious alternatives - repurposing the
> extends or implements keywords would be misleading, since they would work
> precisely the same way; worse, permitting both keywords would render
> consumer code invalid if an upper bound type provided by a library is
> refactored between class and interface. Repurposing instanceof would also
> be misleading, since the upper bound is checking the type-hint, not an
> instance.
>

Why not use "as" which is already the keyword used to define aliases?
Probably of the form class foo<DateTimeInterface as DateType> I think this
feels more natural, as its how we do aliasing with a use statement. Also,
this way it follows the same style as other aliases "RealName as Alias".
I'm not saying is doesn't work, but I wonder if you'd considered as and if
so, why you decided against it.

When autoloading is triggered e.g. by a new statement with a generic type,
> autoloading is triggered as normal, with only the class-name (without type
> parameters) being supplied.
>


In other words, a statement like new Map<int,string>() will trigger
> auto-loading of class Map.


What order are things autoloaded (or does it even matter)? For example,
given the following - does it matter what order things are autoloaded? It
feels like it would but I'm not sure what would get resolved first:

class Gen<IDType, DisplayType, StorageType> {}
class ListGenerator implements HtmlGenerator {}
class FtpWriter extends FileIO {}
new Gen<int, HtmlGenerator, FileIO>(123, new ListGenerator(), new
FtpWriter());

Again, I'm not sure if it matters but would there be any problems (and this
goes to the whole list, since your RFC says you're not a C coder) with the
order of autoloading with relation to resolving validity of types?

In your second example in the Trait section you have:

> class Box<T>
> {
>     use Box<T>;
> }

I think you meant to say "use Container<T>;" as that is the name of your
trait.

Again, really awesome RFC and I hope it can be implemented and accepted!

~Ryan

--089e014935f46c84e60528cba8cb--