Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:80755 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 21304 invoked from network); 18 Jan 2015 17:33:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Jan 2015 17:33:58 -0000 Authentication-Results: pb1.pair.com smtp.mail=morrison.levi@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=morrison.levi@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.179 as permitted sender) X-PHP-List-Original-Sender: morrison.levi@gmail.com X-Host-Fingerprint: 209.85.214.179 mail-ob0-f179.google.com Received: from [209.85.214.179] ([209.85.214.179:53705] helo=mail-ob0-f179.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 18/A1-18613-58EEBB45 for ; Sun, 18 Jan 2015 12:33:57 -0500 Received: by mail-ob0-f179.google.com with SMTP id nt9so25780345obb.10 for ; Sun, 18 Jan 2015 09:33:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=3gkjdiuVP7uPVFmR5EJZbO9hFoXhaoRmfYNfZH+vovg=; b=c0xcPD8Jt5l+hC/hg5bhbqX7UsRhh9GLcnnjE8q+VI60lOVyhezHRjC9zu+sjmD2hi iujumgZiJwsTqY4tXM6fEGapw6MM46IaYJDeoaelAJqsfnJnSEuYmGlG2gurkljRMde1 aFPU9yhRNMW1r0gWEvuPsgzj8vYGRGbVCv9S/+LzLXTmzdv32DUf+sJ6xhtue6IBdg05 PbDQ7vNiRjO+r6MjBhqKSU/lwJbbhl7+KVc8zy70m1H2NcqlKqhlnqOdO+MR0KAjsSkj i5a0H3EJGkGYijEqiqbz7djjcxvw7OPT2hil1wYVw9zAJnvjXlxhic10tmec6mwRNQ6Q qYMA== MIME-Version: 1.0 X-Received: by 10.202.55.198 with SMTP id e189mr14858742oia.80.1421602434552; Sun, 18 Jan 2015 09:33:54 -0800 (PST) Sender: morrison.levi@gmail.com Received: by 10.76.103.101 with HTTP; Sun, 18 Jan 2015 09:33:54 -0800 (PST) In-Reply-To: References: <1CD8C39C-8830-4F95-812D-34DA83A7782F@welsh.co.nz> Date: Sun, 18 Jan 2015 10:33:54 -0700 X-Google-Sender-Auth: Ppy4LYnUkfuIfddyQn8gQbgvNh0 Message-ID: To: Pierre Joye Cc: Yasuo Ohgaki , Simon J Welsh , internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [RFC][Vote] Return Types From: levim@php.net (Levi Morrison) On Sun, Jan 18, 2015 at 9:55 AM, Pierre Joye wrote: > On Sun, Jan 18, 2015 at 11:53 PM, Levi Morrison wrote: >> On Sat, Jan 17, 2015 at 4:42 PM, Yasuo Ohgaki wrote: >>> Hi Pierre and Levi, >>> >>> On Sat, Jan 17, 2015 at 3:05 PM, Pierre Joye wrote: >>>> >>>> On Fri, Jan 16, 2015 at 10:36 PM, Yasuo Ohgaki wrote: >>>> > Hi Simon and Levi, >>>> > >>>> > On Fri, Jan 16, 2015 at 4:53 PM, Simon J Welsh >>>> > wrote: >>>> > >>>> >> The tests have it after the use(): >>>> >> >>>> >> https://github.com/php/php-src/pull/997/files#diff-e306c6e99612ba59b00a4fe435b287e5R9 >>>> >> >>>> >> This was discussed in depth a couple of times in the related threads. >>>> >> >>>> > >>>> > Thank you for the information. It should be in the RFC. IMHO. >>>> > I feels natural to have type spec after function parameter definition >>>> > rather than >>>> > after "use". >>>> >>>> Please do not change the RFC during votes phase, or re start it. >>>> >>>> If many of the voters feel like they were voted on something different >>>> of what is being discussed here, it may be a good thing to restart it. >>>> However I think we all understood it as it is described in this >>>> thread. Let update it after the votes or for the docs. >>> >>> >>> Sounds good to me. >>> Let's update the RFC after vote. >> >> According to the previous discussion the return type goes after the >> use statement, and this is how it is implemented. There has not been >> an unintentional mistake here. >> >> If you disagree with that decision I am open to discussing it again. >> Since it isn't actually mentioned in the RFC (which was an oversight, >> I apologize) I'm not sure we'd have to revote on it. Anyone else have >> an opinion on this? > > Addint/editing it means a re vote. I did not mean editing it during vote; I meant that since the RFC does not actually address this point it isn't technically included in the vote. This means that if it passes we could alter this behavior if desired while still being true to the vote.