Hi, welcome. On first glance code seems good.
This indeed requires an RFC. The detailed process for RFCs is described over at https://wiki.php.net/rfc/howto 🙂

Oh BTW, the CI is failing because you didn't regenerate the arginfo files (or it was, but you didn't add it to your commit).
Normally make regenerates this file from the stub.php file. If it didn't, run ./build/gen_stub.php

Oh BTW, the CI is failing because you didn't regenerate the arginfo files (or it was, but you didn't add it to your commit). Normally make regenerates this file from the stub.php file. If it didn't, run ./build/gen_stub.php

Thank you - really appreciate that 👍

This indeed requires an RFC.

It appears simple and obvious enough to be okay without RFC (not much discussion to be had here), but I'm okay with this going through the RFC process.

Should we also add str_istarts_with and str_iends_with? Naming is not particularly pretty with the second underscore, but that seems most consistent.

This indeed requires an RFC.

It appears simple and obvious enough to be okay without RFC (not much discussion to be had here), but I'm okay with this going through the RFC process.

Considering there is going to be bikeshed, and I don't remember why the last time this was not included, I do think an RFC is probably necessary.

Should we also add str_istarts_with and str_iends_with? Naming is not particularly pretty with the second underscore, but that seems most consistent.

Bikeshed: surely stri_contains and stri_starts_with makes more sense...

It appears simple and obvious enough to be okay without RFC (not much discussion to be had here), but I'm okay with this going through the RFC process.

and I don't remember why the last time this was not included

Already some history posted on the ML, and they're questioning the feature: https://externals.io/message/127504#127505

Thanks all :)
Definitely not precious on where the i goes - will see what other comments we have on the ML.

Because str_ireplace exists, a consistent name would be str_icontains.

Thanks all.

I'll create a RFC for this, and if successful look to do the same with str_​starts_​with and str_ends_with :)