Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78697 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 60744 invoked from network); 5 Nov 2014 01:19:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Nov 2014 01:19:02 -0000 Authentication-Results: pb1.pair.com header.from=morrison.levi@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=morrison.levi@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.175 as permitted sender) X-PHP-List-Original-Sender: morrison.levi@gmail.com X-Host-Fingerprint: 209.85.214.175 mail-ob0-f175.google.com Received: from [209.85.214.175] ([209.85.214.175:59193] helo=mail-ob0-f175.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2C/51-54119-40B79545 for ; Tue, 04 Nov 2014 20:19:00 -0500 Received: by mail-ob0-f175.google.com with SMTP id gq1so6885003obb.20 for ; Tue, 04 Nov 2014 17:18:57 -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=LvlC1KMx2fcevgMZz8H0FzUHc08eUpDyCsdFDyZlZng=; b=enqL8wbZKOM5xhcyfEdWlcrCfV0DsZcH1yZss3BHo6MHH93QB+8GK2VWj8gqGWhWv5 QTMSURqspVVW7mWXZInq59im0b6gc9Ar7WsoNRWuDIYFdEhhj+gVzMkn9aivyMhv+hzY dDyXU9gjuq5LA2BCIAO9zZGlPd1s7Pm9iOb9ZavcZBXEGhx1dnmuG7oLT4PyZyvY2t6c Z2jzmOIDan1axlW2kiqihF2g0KP8l77Tw4Uw7ln9cCCjoIYXoF4G7tDyZKRtOQv+S6au M3WTWPv0d1EdPfBKUFJ6BDAHlVT9SpTCwyADVo6U+I4BEV269FOyCGxQ0zG9VOjzaBwG YNlw== MIME-Version: 1.0 X-Received: by 10.182.65.36 with SMTP id u4mr45712401obs.29.1415150337785; Tue, 04 Nov 2014 17:18:57 -0800 (PST) Sender: morrison.levi@gmail.com Received: by 10.76.159.163 with HTTP; Tue, 4 Nov 2014 17:18:57 -0800 (PST) In-Reply-To: <545977E1.2060700@sugarcrm.com> References: <002601cff777$eb923430$c2b69c90$@tutteli.ch> <000601cff80a$972e0250$c58a06f0$@tutteli.ch> <5458937F.9020304@sugarcrm.com> <545910F1.8030904@sugarcrm.com> <859A97F0-7C58-406A-857B-557F8AA657AD@ajf.me> <545917A2.6000206@lerdorf.com> <545977E1.2060700@sugarcrm.com> Date: Tue, 4 Nov 2014 18:18:57 -0700 X-Google-Sender-Auth: 4zMNM2SYYkO03L2rAEdh4CKjSTk Message-ID: To: Stas Malyshev Cc: Rasmus Lerdorf , Andrea Faulds , Leigh , Robert Stoll , PHP Internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] Types on the right or on the left From: levim@php.net (Levi Morrison) >> Except `static function()` and `static function foo()` already have >> meaning, and if we allowed static return types (very possible) that >> would be ambiguous. This syntax is a no-go. > > If it is possible, why it's not the part of the RFC? Probably because > there's not much place where it would make sense. So, the only > objections so far have been: > > 3. We could somehow in some undefined time in the future allow static > there, even though we're designing it right now and we actually *do not* > allow it and see no reason to allow it. You seem to be under the assumption that I have designed this as THE RFC for return types, and there will be no others. Quite the contrary: it has been designed to be incredibly minimal, and has taken into consideration possible expansions and allowed for them to work. Other examples not already included are generics and function`