Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:97154
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.161.169 cause and error)
MIME-Version: 1.0
In-Reply-To: <CAFMT4Nqiv0ThgVRza2oaReDhGzSN0hOtWLyW=qDvc3yVNhd_AA@mail.gmail.com>
References: <CA+kxMuS7BJyJOo0p-+8CF+bKy5oTLWLJVygA=u89iNHPXjENRQ@mail.gmail.com>
 <CAFMT4Nqiv0ThgVRza2oaReDhGzSN0hOtWLyW=qDvc3yVNhd_AA@mail.gmail.com>
Date: Thu, 24 Nov 2016 08:58:08 +0000
Message-ID: <CA+kxMuQZTLKDDbbJXDjJTkkPCK_0Jfwrek-jVg94x9wEoqQnFw@mail.gmail.com>
To: Levi Morrison <levim@php.net>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Object type hint, now with added variance
From: danack@basereality.com (Dan Ackroyd)

Hi Levi,

On 23 November 2016 at 01:25, Levi Morrison <levim@php.net> wrote:
>
> it assumes that all types that are not statically known to the engine are
> objects. This is a restrictive future compatibility concern.

Any RFC and/or patch can only deal with PHP as it currently is.

> Giving up these options for the sake of object
> variance is definitely not prudent in my opinion.

We would not necessarily be giving them up. We are just adding a small
amount of complexity that would need to be handled by future RFCs.

Which is true of all RFCs.

> For instance enumerations (or enums) are one possible type I can see us
> adding that may not be objects.

I very much look forward to the RFC for enums, and have for some time.
When are you thinking of submitting it for discussion and voting?

cheers
Dan
Ack