Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96559 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 65627 invoked from network); 23 Oct 2016 15:14:35 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Oct 2016 15:14:35 -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.213.181 as permitted sender) X-PHP-List-Original-Sender: morrison.levi@gmail.com X-Host-Fingerprint: 209.85.213.181 mail-yb0-f181.google.com Received: from [209.85.213.181] ([209.85.213.181:35093] helo=mail-yb0-f181.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 72/CF-28528-8D3DC085 for ; Sun, 23 Oct 2016 11:14:33 -0400 Received: by mail-yb0-f181.google.com with SMTP id d128so3911959ybh.2 for ; Sun, 23 Oct 2016 08:14:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=XtBU09+feixrMOMzbKDjKlL6SmSNmKIY7kr5TsI0IlQ=; b=kItBcXNgKDNx/+ZTxn5fYLv43sRkwcMoG6KRQXLCVODlQM4B8186ri5Mm2h+8Mj/xy /1fOGx+XHHAmztA3N6jBCB+ridsA6SZpHTu2m+iqtV3xr24/2XbnEqw9uhTO9JocpbYW Rf7yLGRXaPW8b0kNIPwr4wYmoROEnqtAr4p67vktxXN83HF0REBzuGu9XxURoA+wspgz gYxFOSkFjNn553+/JdlnBFiNmqS5K8+787u651JiR/LbykxROd5eXr6edwWHVDoTg8fq g7LElNhmbYgLl+8Cla1HcVDAd1xIMYcqDr9r4wwePVbVd6dGzt4tuls+v+VkkGLp9176 nHug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-transfer-encoding; bh=XtBU09+feixrMOMzbKDjKlL6SmSNmKIY7kr5TsI0IlQ=; b=Am8awNeJH59xQ5L829tPANWTeqP55BcS3EiDoVSM7wh9Ug7vp2AhTWsh/HPVH8iAKo zEdKUoPiRcsH2uliFCS9YxNxCPlY8X4to3LI0DuZbmo5dD5DrNB4yIqQjtvzjmYFkM7c CFtVq7WUujaw5FWvssJ47igSfey2aKefAjL0a5lV4jTlPAqRqo899NXVBmAkOXNDxxct zbZPEB79/HxowshNZWrapslZkIS4uYr9OXPMWq/aKO101pDxNtGCH9lZKO8oZ630UNkC Wr2ZNBlUCPtgGyjglTqwsB5W6r95shhjoyHXaDDAVOH7FEOKZHSxll82sQau0TypOI7z S52A== X-Gm-Message-State: ABUngvdyxl6I89g5h6MpEcx3iJW0UmpKajrLkuZ6oLNTJiGbcZ8DFhDk1wdO6nsC2G2lbCi2DIWnUzovTW3tpw== X-Received: by 10.37.170.197 with SMTP id t63mr10168422ybi.102.1477235670128; Sun, 23 Oct 2016 08:14:30 -0700 (PDT) MIME-Version: 1.0 Sender: morrison.levi@gmail.com Received: by 10.13.200.3 with HTTP; Sun, 23 Oct 2016 08:14:29 -0700 (PDT) In-Reply-To: References: Date: Sun, 23 Oct 2016 09:14:29 -0600 X-Google-Sender-Auth: BcrOqLpvbIaFx9g-gEca2_D_7Zg Message-ID: To: =?UTF-8?Q?Micha=C5=82_Brzuchalski?= Cc: PHP Internals List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Object type hint From: levim@php.net (Levi Morrison) On Sun, Oct 23, 2016 at 1:39 AM, Micha=C5=82 Brzuchalski wrote: > Hi all, > > I would like to initiate discussion for Object typehint RFC > https://wiki.php.net/rfc/object-typehint > > This feature is developed to provide missing functionality which is neede= d > and quite easy to introduce. > There are many people which I've talked about the benefits of this > functionality. > > For those who doesn't like the idea and think they won't need neither use > it rather than just saying 'no' they > please say why other people who want to use that parameter type are wrong= , > for wanting to do that. > > If there is anything left to discuss, please comment. > > Thanks to @Danack for drafting. > -- > regards / pozdrawiam, > -- > Micha=C5=82 Brzuchalski > about.me/brzuchal > brzuchalski.com I generally don't mind keywords/new classes being added to minor versions. However I am nervous about this one as I am sure there are a lot of `class Object` floating around. Maybe this would be best suited for 8.0 with E_DEPRECATED being emitted to warn people of the up-coming change? Also, can the RFC be edited to give an example of how people will be affected? Other than this issue I support this RFC.