Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128387
Precedence: list
MIME-Version: 1.0
References: <c8a2439d-2690-4e0e-a13b-718714728bd5@app.fastmail.com>
In-Reply-To: <c8a2439d-2690-4e0e-a13b-718714728bd5@app.fastmail.com>
Date: Mon, 4 Aug 2025 14:02:07 -0300
Message-ID: <CAEwRQKbzm_wnzkaSG5VB86Z7j=tfjg+tSMVLv=qYRhC1rtmNSw@mail.gmail.com>
Subject: Re: [PHP-DEV] Blog post: If we can get partial generics, should we?
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
From: carlosv775@gmail.com (Vinicius Dias)

I'm not a voter nor part of the internals, but I'd say "yes", for sure.

One thing that came to mind while reading the article (keep in mind
that I don't have any knowledge on the internals of PHP, so if it's a
dumb question, sorry about that):

Would it be possible to transform (in compile-time), the first option
(that isn't supported) into the second one?

```
// Turning this:
$blogPostRepository = new BaseRepository<BlogPost>();

// Into this:
$blogPostRepository = new class extends BaseRepository<BlogPost> { };
```

If this is possible, although I know it's not ideal, it would allow us
to have that syntax and we wouldn't need to manually create "empty
extending classes".