Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68096 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47641 invoked from network); 11 Jul 2013 19:52:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Jul 2013 19:52:02 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.83 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.83 smtp83.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.83] ([108.166.43.83:56852] helo=smtp83.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F7/64-03322-1EC0FD15 for ; Thu, 11 Jul 2013 15:52:01 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id E0C9C503D2; Thu, 11 Jul 2013 15:51:58 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 5CF5C503BE; Thu, 11 Jul 2013 15:51:58 -0400 (EDT) Message-ID: <51DF0CDD.7060108@sugarcrm.com> Date: Thu, 11 Jul 2013 12:51:57 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Florin Patan CC: Sara Golemon , "RQuadling@gmail.com" , PHP internals References: <1372258135.2410.22.camel@guybrush> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Request for comments - new PHP feature: return typing From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Thanks for your input Sara, everything sounds very interesting. In all > fairness I haven't looked at HHVM but I from what you described about > this particular feature sounds good. > > Should I conclude that there's enough interest for this feature and > move from a gist to a RFC? If so, I would definitely need someone to > help out with the implementation. We already have a bunch of RFCs about strict typing in PHP: https://wiki.php.net/rfc/typechecking So I personally am not sure we need yet another RFC on the topic - given that we discussed previous ones multiple times. While HHVM is a very interesting project, their use case is pretty specific and narrow, and, as I understand, connected to a single application (albeit running huge traffic numbers). So I'm not sure copying whatever they do is necessarily good for PHP as a whole. HHVM case is basically static compilation of monolithic application, as far as I remember, which is not how PHP is usually run. It is true that such mode negates many arguments against static typing, but it negates them only for specific narrow case of HHVM, not for PHP as a whole. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227