Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123393
Content-Type: multipart/alternative;
 boundary="------------PUZYMJZcjljGuxt3Y0s7GWUs"
Message-ID: <3cac0454-ceb2-449a-8b9a-1fac3f866a9c@scriptfusion.com>
Date: Wed, 22 May 2024 00:47:42 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] [Discussion] Implicitly backed enums
To: internals@lists.php.net
References: <fcb90d5b-ac31-49b5-bf72-ed8654c34053@scriptfusion.com>
 <da922505-5cb3-44ac-916c-fbb7f864707b@app.fastmail.com>
 <99c30f5d-e2f3-4027-a8fc-b3b9c71fb6d1@scriptfusion.com>
 <1286eed1-c35e-40ec-a6f0-84926c99c911@app.fastmail.com>
Content-Language: en-GB
In-Reply-To: <1286eed1-c35e-40ec-a6f0-84926c99c911@app.fastmail.com>
From: bilge@scriptfusion.com (Bilge)

This is a multi-part message in MIME format.
--------------PUZYMJZcjljGuxt3Y0s7GWUs
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

On 22/05/2024 00:31, Larry Garfield wrote:
> I could see an argument for auto-populating the backing value off the 
> enum name if it's not specified, something like this:
> enum Options: string {
>    case First; // This implicitly gets "First"
>    case Second = '2nd';
> }

This seems like a reasonable compromise. In this case, all I need to do 
is change my enum to a backed enum (suffix `: string`) and I get the 
benefits of implicit values. I still like the idea of the same being 
possible for non-backed enums, though I imagine that is a product of my 
naïveté, as I do not tend to think of things in the framing of 
(de)serialization.

> I'm not sure if I'd support it myself at the moment

Noted, but I once again find myself needing to ask: why not? Were it up 
to me, I'd say let's start right now! :)

Aside, I am not at all concerned with integer-backed enums at this 
juncture, and presume that could be a separate discussion/implementation 
anyway.

Cheers,
Bilge

--------------PUZYMJZcjljGuxt3Y0s7GWUs
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 22/05/2024 00:31, Larry Garfield
      wrote:<span style="white-space: pre-wrap">
</span></div>
    <blockquote type="cite"
      cite="mid:1286eed1-c35e-40ec-a6f0-84926c99c911@app.fastmail.com"><span
      style="white-space: pre-wrap">I could see an argument for auto-populating the backing value off the enum name if it's not specified, something like this:</span>
      <pre class="moz-quote-pre" wrap="">
enum Options: string {
  case First; // This implicitly gets "First"
  case Second = '2nd';
}</pre>
    </blockquote>
    <p>This seems like a reasonable compromise. In this case, all I need
      to do is change my enum to a backed enum (suffix `: string`) and I
      get the benefits of implicit values. I still like the idea of the
      same being possible for non-backed enums, though I imagine that is
      a product of my naïveté, as I do not tend to think of things in
      the framing of (de)serialization.</p>
    <blockquote type="cite"
      cite="mid:1286eed1-c35e-40ec-a6f0-84926c99c911@app.fastmail.com">
      <pre>I'm not sure if I'd support it myself at the moment</pre>
    </blockquote>
    <p>Noted, but I once again find myself needing to ask: why not? Were
      it up to me, I'd say let's start right now! :)</p>
    <p>Aside, I am not at all concerned with integer-backed enums at
      this juncture, and presume that could be a separate
      discussion/implementation anyway.<br>
    </p>
    <p>Cheers,<br>
      Bilge<br>
    </p>
    <p></p>
    <p><span style="white-space: pre-wrap">
</span></p>
  </body>
</html>

--------------PUZYMJZcjljGuxt3Y0s7GWUs--