Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96811 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 37655 invoked from network); 10 Nov 2016 10:38:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Nov 2016 10:38:45 -0000 Authentication-Results: pb1.pair.com header.from=pthreads@pthreads.org; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=pthreads@pthreads.org; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pthreads.org from 74.125.82.47 cause and error) X-PHP-List-Original-Sender: pthreads@pthreads.org X-Host-Fingerprint: 74.125.82.47 mail-wm0-f47.google.com Received: from [74.125.82.47] ([74.125.82.47:37773] helo=mail-wm0-f47.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4C/70-15787-33E44285 for ; Thu, 10 Nov 2016 05:38:43 -0500 Received: by mail-wm0-f47.google.com with SMTP id t79so22324132wmt.0 for ; Thu, 10 Nov 2016 02:38:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pthreads-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kLGCHpjjLOtj/nZtTES1K87DERSETAF7N8SKpKHm+Kk=; b=MUfbXZyPAMcywe7NBt1KA/mWm+3vi/6dZSP0fHWHfex3LfxswdsCngnkFF0hgi+WC4 Rk/vGzeOxQwvUQCJD/ugo74W5zV/k9XnmkhSE0rXiFOE7OGjV91u91ebQTMQAI51groM +By9KwZO9LqbIrPk+8NiIv7QwRnrxuVC1DZC1BmLFedjp/8Wr0a3nQpamshpy9VdawNK M/Lq7YHLJpTaPE22F/WKBZ0LGvJ34SZsryq5rDMI8n5fauz5jMIB2wGVq52cSQnGMohD cEW9e5UdPWzn920Qp6u6lCzZ0P/Ka6OT+R8cbj3a0ZZIYM5juutBdrrZuVt9XQJC7wma gYlw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=kLGCHpjjLOtj/nZtTES1K87DERSETAF7N8SKpKHm+Kk=; b=jBJ/iBkdyCiRijogGExFCHV2yYt1ruYy3q8gT5fhuBdqnDNghJvGvbbW6yBIl1fQYh 2BetOjvOPUb1d8VRvnaTJCqSETn/zPDpMR16iLIDdr+/LvxAGUOwbH1paFjbLVx0RF6y aExXFfmeoBAji7NPSxHvQG7MywTzi/v9z2bHz8mF0VXEgFwYy6lqQKh3AK01pPvl6BUe KR8sJ9QfIqVTA0Ga1c1lHksKDFEf+XdIITeYOrFvEk95Owx+Y7nY4Z4zYjoBqbOeQnvd pH4I+w7/FOSrUn8UrygQiZ2D3iVOuu5rsKz89cNW0uZlbaWz17487xTv9vbwGnJPrbGV mZ9w== X-Gm-Message-State: ABUngvdLYPTDTS0DQvwc3n8XFtGdhyJmFuR0yi1rcWcvXhUzZn648rPaqX8rvR8FDSDzVqmKcMygi+vAs3BHVg== X-Received: by 10.194.116.225 with SMTP id jz1mr3787022wjb.224.1478774320834; Thu, 10 Nov 2016 02:38:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.80.161.230 with HTTP; Thu, 10 Nov 2016 02:38:40 -0800 (PST) X-Originating-IP: [109.157.245.230] In-Reply-To: References: <0c171a20-c72d-4157-1117-6628a52dd1f0@gmx.de> Date: Thu, 10 Nov 2016 10:38:40 +0000 Message-ID: To: Peter Cowburn Cc: Niklas Keller , "Christoph M. Becker" , =?UTF-8?Q?Micha=C5=82_Brzuchalski?= , PHP Internals List Content-Type: multipart/alternative; boundary=001a1130ca9218afec0540effa26 Subject: Re: [PHP-DEV] [RFC][VOTE] Object typehint From: pthreads@pthreads.org (Joe Watkins) --001a1130ca9218afec0540effa26 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Morning Peter, > I'll put RFC: On hold, then apply patch, draft some info in RFC and then set up new voting. Just a few messages up from here ... Would you prefer a new thread to make that announcement (I think it may be better) ? Cheers Joe On Thu, Nov 10, 2016 at 9:52 AM, Peter Cowburn wrote: > > > On 10 November 2016 at 09:11, Niklas Keller wrote: > >> 2016-11-09 21:53 GMT+01:00 Christoph M. Becker : >> >> > On 09.11.2016 at 17:28, Joe Watkins wrote: >> > >> > > I want to explain why I voted no on this: >> > > >> > > I think it's significantly less useful without variance, varianc= e >> is >> > > something that is usually difficult to achieve in PHP, but not for >> this >> > > feature in particular. >> > >> > Can you please elaborate what you mean with variance? I see some >> > practical use cases for covariance of a method with return type object= , >> > but I don't see how contravariance could be achieved for parameters of >> > type object. >> > >> > If your suggestion is only about invariance of object return types, I'= m >> > not sure if this very special case would make sense (for consistency >> > reasons). >> > >> >> We already have it for iterable -> array. We would have it for all other >> types if there wouldn't be an implementation issue. >> >> Regards, Niklas >> >> Cheers, >> > Christoph >> > >> > > I absolutely want it, but I want it to be properly useful. >> > > >> > > If the RFC were halted and patched to include variance, I'd +1 i= t. >> > > >> > > Cheers >> > > Joe >> > > >> > > On Sun, Nov 6, 2016 at 5:28 PM, Micha=C5=82 Brzuchalski >> > > .com> >> > > wrote: >> > > >> > >> Hi everyone, >> > >> >> > >> Two weeks have passed since this RFC was put to discussion here. >> > >> >> > >> Therefore, I'm going to put it to a vote for inclusion in PHP 7.2. >> > >> >> > >> Voting starts today, 2016-11-06, and will close after two weeks on >> the >> > >> Sunday 2016-11-20 at midnight. >> > >> >> > >> The RFC and voting widget can be found here: >> > >> https://wiki.php.net/rfc/object-typehint >> > > The vote appears to be closed right now, did I miss an announcement? > > >> >> > >> >> > >> It's a normal 2/3 majority required vote. >> > >> >> > >> Thanks! >> > >> -- >> > >> regards / pozdrawiam, >> > >> -- >> > >> Micha=C5=82 Brzuchalski >> > >> about.me/brzuchal >> > >> brzuchalski.com >> > >> >> > > >> > >> > >> > -- >> > PHP Internals - PHP Runtime Development Mailing List >> > To unsubscribe, visit: http://www.php.net/unsub.php >> > >> > >> > > --001a1130ca9218afec0540effa26--