Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:97155 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 3073 invoked from network); 24 Nov 2016 09:35:56 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Nov 2016 09:35:56 -0000 Authentication-Results: pb1.pair.com smtp.mail=me@kelunik.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=me@kelunik.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain kelunik.com from 81.169.146.163 cause and error) X-PHP-List-Original-Sender: me@kelunik.com X-Host-Fingerprint: 81.169.146.163 mo4-p00-ob.smtp.rzone.de Received: from [81.169.146.163] ([81.169.146.163:27933] helo=mo4-p00-ob.smtp.rzone.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 54/B1-21589-874B6385 for ; Thu, 24 Nov 2016 04:35:53 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1479980149; l=3920; s=domk; d=kelunik.com; h=Content-Type:Cc:To:Subject:Date:From:References:In-Reply-To: MIME-Version; bh=fXkXtI9ZigIHxV4QCV6U7EsOzBUBgvbPpymrtmLpbdI=; b=kWFErBk96eOiUD0oAp+8vLQ761vmIqTjikjTMiZZR69LajqeZK1joIpKGzu0JsKjuk cFJVillsY69Cjg84ywU0BYC7mt0GU4mNKb/spX2kpZcpAgOBg+WI5YsZUnTJpIg+NFAf hu+Y3X/4bktu7gc0pftcv20A2r572mIUshjSs= X-RZG-AUTH: :IWkkfkWkbvHsXQGmRYmUo9mls2vWuiu+7SLDup6E67mzuoNPBqD+ufg= X-RZG-CLASS-ID: mo00 Received: from mail-wj0-f169.google.com ([209.85.210.169]) by smtp.strato.de (RZmta 39.9 AUTH) with ESMTPSA id e04bc2sAO9ZnJ0E (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp384r1 with 384 ECDH bits, eq. 7680 bits RSA)) (Client did not present a certificate) for ; Thu, 24 Nov 2016 10:35:49 +0100 (CET) Received: by mail-wj0-f169.google.com with SMTP id xy5so28984197wjc.0 for ; Thu, 24 Nov 2016 01:35:49 -0800 (PST) X-Gm-Message-State: AKaTC025FMOSri9VT859RZPhWoaVQxYz1WP1GNsNy57sBY/SLwmaBSrnGN+XgqPJ0aB2cWzq+tMsdVEepu4Rww== X-Received: by 10.194.164.226 with SMTP id yt2mr1520414wjb.201.1479980149318; Thu, 24 Nov 2016 01:35:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.80.135.133 with HTTP; Thu, 24 Nov 2016 01:35:48 -0800 (PST) In-Reply-To: References: Date: Thu, 24 Nov 2016 10:35:48 +0100 X-Gmail-Original-Message-ID: Message-ID: To: Dan Ackroyd Cc: Levi Morrison , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=089e0117740f133155054208bbad Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Object type hint, now with added variance From: me@kelunik.com (Niklas Keller) --089e0117740f133155054208bbad Content-Type: text/plain; charset=UTF-8 2016-11-24 9:58 GMT+01:00 Dan Ackroyd : > Hi Levi, > > On 23 November 2016 at 01:25, Levi Morrison 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. No. We had a similar discussion for the context sensitive lexer RFC and didn't allow some things to make future features easier. > > 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. > It's not a small amount of complexity, otherwise we'd already have contra / covariance. Regards, Niklas > 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 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --089e0117740f133155054208bbad--