Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84796
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.175 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <CANUQDCjK7F1H5PZeV4XXvbDOsmyYtG4P1fPH3QnKBuY9EM-JdA@mail.gmail.com>
References: <CANUQDCjK7F1H5PZeV4XXvbDOsmyYtG4P1fPH3QnKBuY9EM-JdA@mail.gmail.com>
Date: Sun, 15 Mar 2015 11:11:10 +0900
Message-ID: <CAGa2bXZGQM_SW5aOz9+HmtWJcd=Ne2ipcTVQjk=MzfdGJFCF1w@mail.gmail.com>
To: Niklas Keller <me@kelunik.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b2e4858b5bf5205114a416a
Subject: Re: [PHP-DEV] [RFC][PRE-VOTE] In Operator
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--047d7b2e4858b5bf5205114a416a
Content-Type: text/plain; charset=UTF-8

Hi Niklas,

On Sun, Mar 15, 2015 at 9:54 AM, Niklas Keller <me@kelunik.com> wrote:

> I'd like to announce that I'll open the vote for the in operator later
> that day.
> You can find the RFC here: https://wiki.php.net/rfc/in_operator
>
> There was a small change: If the haystack is a string, integers are no
> longer allowed as needle. This change was necessary so it's
> consistently strict for both, array and string haystacks.
>

I would vote "no".

1. PHP is weakly typed (well at least it is currently)
2. "in" operator does not work well enough for weakly typed types
3. We have discussions how PHP should be type aware currently

These are reasons why I would vote "no" for this now.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--047d7b2e4858b5bf5205114a416a--