On Thu, 17 Sept 2026, 00:50 Kamil Tekiela, <[email protected]> wrote:
> On Wed, 16 Sept 2026 at 15:19, سپهر محمودی <[email protected]> > wrote: > > > > Does anyone here actually dislike my contributions to php-src???? > > Yes. > Yes from me as well. I don't know why you are persisting with this RFC. I don't remember ever seeing so much mail in the list for such an unwanted RFC. I could understand if during the discussion stage, you got feedback like: "OMG, I soooo need this." or "Finally! This has always been sorely missing from the language." but that didn't happen. I hope you are not motivated to contribute just so you can be considered a contributor. I hope ego or prestige is not behind the unrelenting push. Even if you can build a faster version in C, that doesn't mean it should be added to the `array_` functions family. I am sure dozens of callback hybridized iterator functions could be written faster in C, but that is not a green light to flood the core with more native functions. As I mentioned previously, please silently compile your own list of proposals. Once you have ~5 separate deeply-considered proposals that you are proud of, then self-assess which is best and if it is worthy of sharing. I have personally considered proposing `array_transpose()`, `preg_escape()`, a `PREG_` flag that omits unwanted full string matches, making the third parameter of substr_replace() null by default to allow suffixing an array of strings, and adopting `..` range syntax across all native functions which accept a character mask, but none of my arguments feel like they would garner support. So, I'm keeping them locked away in my mental vault. Maybe I'll have an epiphany that will make them attractive or maybe they'll shape my thoughts on another idea. Not all ideas are winners, that doesn't make someone a loser. Just keeping learning and growing. Sincerely, mickmackusa >
