Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115730
MIME-Version: 1.0
References: <CAMrTa2HYeKaE9E+A81HvSykpAD8ctd6aK9vtg_U15bYjyjzLKA@mail.gmail.com>
 <CAKuGYLSMY3WeUPe+LOBB_nSn3u-C_Pk3cnh0KDeKsSkjA7bTFQ@mail.gmail.com> <39B2655D-3877-41C1-9112-E2772E44544D@gmail.com>
In-Reply-To: <39B2655D-3877-41C1-9112-E2772E44544D@gmail.com>
Date: Sat, 14 Aug 2021 10:21:18 -0700
Message-ID: <CAMrTa2EbXjA_aZpxj+c36Coc4JZB6EsE3fv_PEoYVRq4f6oyXQ@mail.gmail.com>
To: Claude Pache <claude.pache@gmail.com>
Cc: Matthew Brown <matthewmatthew@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000075821d05c988327a"
Subject: Re: [PHP-DEV] [RFC] Never For Argument Types
From: jordan.ledoux@gmail.com (Jordan LeDoux)

--00000000000075821d05c988327a
Content-Type: text/plain; charset="UTF-8"

On Sat, Aug 14, 2021 at 10:12 AM Claude Pache <claude.pache@gmail.com>
wrote:

>
> If users of that interface would suddenly be *required* to specify a
> parameter type, whereas previously they were *forbidden* to specify one,
> except a meaningless `mixed`... it would be not nice and useless.
>
> Moreover, note that `mixed` was only introduced very recently, in 8.0: so
> that, it would be impossible to implement `ArrayAccess` on code that work
> both in 7.x and a future version with the updated interface. Not only would
> it be not nice, but it would be positively harmful.
>
>
Those are some excellent points I hadn't considered. I will remove the
explicit widening from this RFC and update my pull request. I was
considering having that aspect as a separate vote, but this point about
mixed being a recent addition was a point I hadn't considered, and to me
suggests that it shouldn't even be an option in the RFC, particularly
because we would like to update the ArrayAccess interface and that will
affect a lot of existing code.

Jordan

--00000000000075821d05c988327a--