Re: [RFC][DISCUSSION] Object type hint
| From: | Levi Morrison | Date: | Sun, 23 Oct 2016 15:14:29 +0000 |
| Subject: | Re: [RFC][DISCUSSION] Object type hint | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-96559@lists.php.net to get a copy of this message | ||
On Sun, Oct 23, 2016 at 1:39 AM, Michał Brzuchalski
<michal@brzuchalski.com> 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 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ł 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.