On 29.05.2025 23:00, Kamil Tekiela wrote:
As I understand, it was a conscious decision not to add this function
when str_contains was created. The reason is that case sensitivity is
locale-dependent, and for such use cases, mbstring extension is better
[1] & [2]. Do you think that locale is a con
On 29 May 2025 22:00:00 BST, Kamil Tekiela wrote:
>As I understand, it was a conscious decision not to add this function
>when str_contains was created. The reason is that case sensitivity is
>locale-dependent, and for such use cases, mbstring extension is better
>[1] & [2]. Do you think that loca
As I understand, it was a conscious decision not to add this function
when str_contains was created. The reason is that case sensitivity is
locale-dependent, and for such use cases, mbstring extension is better
[1] & [2]. Do you think that locale is a concern here, and if not,
why? Would it be a go
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
On Wed, May 28, 2025 at 2:01 PM carlos_silva
wrote:
> Hello everyone.
>
> I've been thinking about core developers these days, and I'm happy to see
> the PHP foundation growing, and more and more new developers arriving,
> eager to push PHP forward.
>
> But at the same time, I have the feelin
Hello, Carlos!
Thank you for your support.
I feel like I should add a bit of jam to this story and share some news.
When I set the two-week limit for the vote, Roman Pronskiy reached out
to me almost immediately and offered direct contact with PHP CORE.
I received maximum support and valuable adv
