Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126722
Feedback-ID: i8414410d:Fastmail
Precedence: bulk
MIME-Version: 1.0
Date: Tue, 11 Mar 2025 16:45:46 -0500
To: "php internals" <internals@lists.php.net>
Message-ID: <3e35cd25-c851-4ecc-8a1b-102dadb226e5@app.fastmail.com>
In-Reply-To: 
 <CALaXqqRWL8ygMGoA5xnMtt7w6rE-5WJJZ5P9oiO3vHgqvod=Fw@mail.gmail.com>
References: 
 <CALaXqqRWL8ygMGoA5xnMtt7w6rE-5WJJZ5P9oiO3vHgqvod=Fw@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] [Discussion] Never parameters
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: larry@garfieldtech.com ("Larry Garfield")

On Mon, Mar 10, 2025, at 2:05 PM, Daniel Scherzer wrote:
> Hi internals,
>
> I'd like to start discussion on a new RFC about allowing `never` for 
> parameter types when declaring a method.
>
> * RFC: https://wiki.php.net/rfc/never-parameters-v2
> * Implementation: https://github.com/php/php-src/pull/18016
>
> -Daniel

I have a use case for this in Serde, so would be in favor.

We should not block this kind of improvement on the hope of generics.  Worst case, we have this plus generics so you have options, how terrible.

Rust-style associated types would probably work as well.  I'd be fine with that approach, too.  One could argue they're more valuable as a sort of "junior generics," but absent anyone able and willing to implement them, again, worst-case we end up with options in the future.

--Larry Garfield