On Sun, Oct 23, 2016 at 5:14 PM, Levi Morrison <le...@php.net> wrote:
> On Sun, Oct 23, 2016 at 1:39 AM, Michał Brzuchalski > <mic...@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. > 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
