Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127504
Precedence: bulk
MIME-Version: 1.0
Date: Thu, 29 May 2025 21:29:18 +0100
Message-ID: <CADuktwNsNK3vRyJqBwMDL07cy1GAGVCkBpCxAs5DTzfEqVy86Q@mail.gmail.com>
Subject: [PHP-DEV] Adding in a case-insensitive version of str_contains
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary="0000000000009873e606364c27f2"
From: adamcable@gmail.com (Adam Cable)

--0000000000009873e606364c27f2
Content-Type: text/plain; charset="UTF-8"

As a PHP developer of 20 years I'm somewhat accustomed to adding "i" into
the function name when I'm after a case-insensitive version.

Therefore, I found it a bit odd I couldn't do it with the new
"str_contains" function, so have built a basic ci version @
https://github.com/php/php-src/pull/18705

I appreciate that there may be a bit of negative reaction about adding such
a basic function that can so easily be written in user-land. But for me, as
an average PHP coder, I think it's useful to try and fill in gaps which can
cause head-scratching.

Thanks,
Adam

--0000000000009873e606364c27f2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">As a PHP developer of 20 years I&#39;m somewhat accustomed=
 to adding &quot;i&quot; into the function name when I&#39;m after a case-i=
nsensitive version.<br><br>Therefore, I found it a bit odd I couldn&#39;t d=
o it with the new &quot;str_contains&quot; function, so have built a basic =
ci version @ <a href=3D"https://github.com/php/php-src/pull/18705">https://=
github.com/php/php-src/pull/18705</a><br><br>I appreciate that there may be=
 a bit of negative reaction about adding such a basic function that can so =
easily be written in user-land. But for me, as an average PHP coder, I thin=
k it&#39;s useful to try and fill in gaps which can cause head-scratching.<=
br><br>Thanks,<br>Adam</div>

--0000000000009873e606364c27f2--