Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130308
Feedback-ID: i8414410d:Fastmail
Precedence: list
MIME-Version: 1.0
Date: Fri, 13 Mar 2026 09:54:18 -0500
To: "php internals" <internals@lists.php.net>
Message-ID: <7cd8c674-c2ba-494b-8494-3f8dddac1bb8@app.fastmail.com>
In-Reply-To: 
 <CALaXqqRaZRefdqq1=R_hiuGfesOAnwhcC=RwYXLzykYQ2rodgQ@mail.gmail.com>
References: 
 <CALaXqqRaZRefdqq1=R_hiuGfesOAnwhcC=RwYXLzykYQ2rodgQ@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] [Discussion] Debugable enums
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: larry@garfieldtech.com ("Larry Garfield")

On Thu, Mar 12, 2026, at 7:05 PM, Daniel Scherzer wrote:
> Hi internals,
>
> I'd like to start the discussion for a new RFC about removing the 
> prohibition on __debugInfo() methods on enums.
>
> * RFC: https://wiki.php.net/rfc/debugable-enums
> * Implementation: https://github.com/php/php-src/pull/21425
>
> This is a replacement of my earlier RFC to allow __toString() based on 
> the feedback in that discussion, see 
> https://news-web.php.net/php.internals/129540.
>
> Thanks,
> -Daniel

I'm not entirely sure this has much value, but it also seems to not have much downside.  The main argument I could see for holding off is that whenever it is we get to ADTs, we may want a more complex default implementation.  But that would still presumably allow being overridden, like any other class, so it doesn't seem like a landmine to me.  This doesn't have the same semantic issues that __toString() has (and have been discussed elsewhere).

--Larry Garfield