Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96561 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 67302 invoked from network); 23 Oct 2016 15:23:29 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Oct 2016 15:23:29 -0000 Authentication-Results: pb1.pair.com smtp.mail=nikita.ppv@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=nikita.ppv@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.53 as permitted sender) X-PHP-List-Original-Sender: nikita.ppv@gmail.com X-Host-Fingerprint: 74.125.82.53 mail-wm0-f53.google.com Received: from [74.125.82.53] ([74.125.82.53:37232] helo=mail-wm0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 67/10-28528-BE5DC085 for ; Sun, 23 Oct 2016 11:23:24 -0400 Received: by mail-wm0-f53.google.com with SMTP id f193so71326642wmg.0 for ; Sun, 23 Oct 2016 08:23:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lxXw5u83rGx7Mxi5Ts+tQV3MGRiX9FUtInZSCKDAD9w=; b=VZ39Oh6zeQk6uncah6NO6lLvbiDngkoGJIIGHvitLOVInnkxaKRKDFxAE7J+XwqLw2 D1EN0hOlIJuxhqOu9apd2uUTtQgv4Be3Qg9iVoCkq6jAu14D4SLsi8kH0om2q6XlFJhQ msk+UH0uUZ9JxVMRgLHtIG9pgNILGGICelujM0vEgdhojpk05TaEwDf5K5nZOPnV9m+b q6D64Xty1xpYNvPx7GecWYiyGD0kAQFg9AFspCf+06hYEh+zSVZLVriqyFjEjvBdWWFx Et1oiy8kZ2oKeURGhZXw9aE2cJGio8jbvsLjnsZZ7H4YGnVkWieMOjLzLG/hhqboxZcF 8HxA== 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=lxXw5u83rGx7Mxi5Ts+tQV3MGRiX9FUtInZSCKDAD9w=; b=hTbtNUWU0oIxJnmoVDTBo0V3qXslAjKiu9jmF0ifpaaKeEJapjdXYwnp17d8Y4XzpI 9CsZBBShGFsEHdyhGW6xDHWXCWL5M18dD2vSBV9QewbHU3mlzFyoHPVJnPpNUczdT9FP LSDYoLRM4V32wDyKZwue1Dgl+XvErMrubXqtw9+Q2c0lrs6NjYi7utswxxf0Y+5zbV+q H0G1cL93TtJrjz3x80g7qJlbpQrWzl+P/HafbPI8iDwFJTuumlp7IEtIYTSWGOcuvUx+ 3BsuHYkzgzGawGfPjbr7W/QruH737eKNsEJ1L+9uGtAxgJ6p1F46F1QoRyC4mf8yN0jN XjNA== X-Gm-Message-State: ABUngve/go5CVBBXTInFNCmwIJj9Ct5DPMXOyGAX0ellhbO+RwLAZyHhO62Gjc1H4Xfky8pfu5P3D1QGBfn2cw== X-Received: by 10.194.117.10 with SMTP id ka10mr10303490wjb.148.1477236200206; Sun, 23 Oct 2016 08:23:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.129.225 with HTTP; Sun, 23 Oct 2016 08:23:19 -0700 (PDT) In-Reply-To: References: Date: Sun, 23 Oct 2016 17:23:19 +0200 Message-ID: To: Levi Morrison Cc: =?UTF-8?Q?Micha=C5=82_Brzuchalski?= , PHP Internals List Content-Type: multipart/alternative; boundary=001a1130ce5af678f0053f89da20 Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Object type hint From: nikita.ppv@gmail.com (Nikita Popov) --001a1130ce5af678f0053f89da20 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sun, Oct 23, 2016 at 5:14 PM, Levi Morrison wrote: > 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 > needed > > 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 u= se > > 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. > Without commenting on the proposal itself, we did explicitly reserve the "object" typehint in PHP 7: https://wiki.php.net/rfc/reserve_even_more_types_in_php_7 While this reservation does not carry a runtime error, we do document that "usage of them is highly discouraged since they may be used in future versions of PHP." As such, we have given advance warning that this was likely to happen= . Nikita --001a1130ce5af678f0053f89da20--