Re: [VOTE] [RFC] Bound-Erased Generic Types
| From: | Matthew Brown | Date: | Mon, 15 Jun 2026 03:46:21 +0000 |
| Subject: | Re: [VOTE] [RFC] Bound-Erased Generic Types | ||
| Groups: | php.internals | ||
| Request: | Send a blank email to internals+get-131254@lists.php.net to get a copy of this message | ||
> On Jun 14, 2026, at 4:07 pm, Larry Garfield <larry@garfieldtech.com> wrote:
> OTOH, generics getting voted down (for whatever reason) would be... very bad press, both within
> the community and externally.
I think you’re overstating the external impact. This would have been bad PR a decade ago, but
today PHP language evolution is not front of mind for many outside the PHP community.
I believe (from discussions in the list and online) that most of the people who voted it down have
done so due to a very clear philosophical objection to partially-erased types. Those people do not
want the biggest potential follow-on from this RFC, which is language support for erased generic
array<string>, a construct which has existed in docblocks for a couple of
decades.
I think it’s useful to have these decisions written in stone.
I don’t believe there’s a better proposal for erased generics than this one. In the future, when
someone asks why PHP doesn’t have erased generics, we can point to this vote.
Best wishes,
Matt