Re: [PHP-DEV] [VOTE] User Defined Operator Overloads

On Sun, Jan 2, 2022 at 5:07 PM Marco Pivetta wrote: > Hey Jordan, > > I've voted "no" on this one: infix functions may have been interesting, > but adding a whole new type system around operators is really not worth it, > given: > > * Added AST nodes > * Added method definitions for niche

Re: [PHP-DEV] [VOTE] User Defined Operator Overloads

Hey Jordan, I've voted "no" on this one: infix functions may have been interesting, but adding a whole new type system around operators is really not worth it, given: * Added AST nodes * Added method definitions for niche use-cases * Complexity in support for static analysis tools I

[PHP-DEV] [VOTE] User Defined Operator Overloads

Hello internals, I've opened voting on https://wiki.php.net/rfc/user_defined_operator_overloads. The voting will close on 2022-01-17. To review past discussions on this RFC and the feature in general, please refer to: - https://externals.io/message/116611 | Current RFC discussion -

Re: [PHP-DEV] Allowing NULL for some internal functions

On Sun, 2 Jan 2022 at 14:22, Andreas Leathley wrote: > I don't think the current deprecation notices are a real hindrance in > upgrading to a newer PHP version. Nice, but I suspect your code doesen't exactly represents most code :-) And while these may be "small adaptions", I work with some

Re: [PHP-DEV] Allowing NULL for some internal functions

On Sun, 2 Jan 2022 at 13:41, Christoph M. Becker wrote: > [...] > And then it's totally unclear to me how this is supposed to affect > strict_types=1. > [...] > If the BC break is deemed to serious (maybe for string parameters only), > we better consider to undeprecate this, although that would

Re: [PHP-DEV] Allowing NULL for some internal functions

Thanks Allen, Before I start, the RFC is still a Draft, and I'm trying to find a solution... I'll also use a bit of sarcasm, just to be entertaining/funny, so it's not a page of boring technical stuff, I'm not arguing or saying you're wrong, and I genuinely appreciate your views on this. On

Re: [PHP-DEV] RFC: Stop to automatically cast numeric-string to intwhen using them as array-key

On 02.01.2022 at 15:12, Nick Wallace wrote: > I've sent a few emails to unsubscribe. Please remove me from this list. I'm > tired of these fucking emails about a dead language Please send mail to to trigger the unsubscription process. See for

Re: [PHP-DEV] Allowing NULL for some internal functions

On 02.01.22 00:17, Craig Francis wrote: I've spent a few days coming up with a short(ish) list of parameters that are likely to receive `NULL`. The focus is on making it easier for developers to upgrade to newer versions of PHP. I'm thinking of the typical developer, probably using WordPress,

Re: [PHP-DEV] RFC: Stop to automatically cast numeric-string to int when using them as array-key

I've sent a few emails to unsubscribe. Please remove me from this list. I'm tired of these fucking emails about a dead language On Sat, Jan 1, 2022, 8:41 AM Rowan Tommins wrote: > On 31/12/2021 00:21, Kirill Nesmeyanov wrote: > > I support this behavior fix because in its current form, due to a

Re: [PHP-DEV] Allowing NULL for some internal functions

On 02.01.2022 at 00:17, Craig Francis wrote: > On Thu, 2 Dec 2021 at 15:19, Sara Golemon wrote: > >> On Thu, Dec 2, 2021 at 8:48 AM Craig Francis >> wrote: >> >>> Is there any value in me proposing an RFC to update *some* internal >>> functions so they can accept NULL? >> >> I'm not hard

Re: [PHP-DEV] RFC: Stop to automatically cast numeric-string to int when using them as array-key

On 2 January 2022 03:47:11 GMT, Kirill Nesmeyanov wrote: > >I just gave an example of what at the moment can cause an exception in any >application that is based on the PSR. It is enough to send the header "0: >Farewell to the server". In some cases (for example, as is the case with

Re: [PHP-DEV] Allowing NULL for some internal functions

On 01/01/2022 23:17, Craig Francis wrote: I've spent a few days coming up with a short(ish) list of parameters that are likely to receive `NULL`. The focus is on making it easier for developers to upgrade to newer versions of PHP. I'm thinking of the typical developer, probably using WordPress,