Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112746
To: internals@lists.php.net
References: <eadd4a32-a05b-463b-a91f-a5d353c577b2@www.fastmail.com>
 <8aa05350-05fc-df9d-e5d6-fa0f4feb57ba@alec.pl>
 <fdbc8779-de22-46a1-ab6e-e3cfb34565b4@www.fastmail.com>
 <c3dfee4f-6f54-9b4a-a599-fb016ed6a110@alec.pl>
 <4eec7448-f7ab-9955-8c2d-68cd4f822535@gmail.com>
 <7d8ce2a2-8d85-4312-af22-da643faa3a7f@www.fastmail.com>
 <1BC8BF20-B961-4360-855B-5BB95338BB8A@newclarity.net>
Message-ID: <d07b38e1-78f9-822e-f3be-a4ed42b6702b@fischer.name>
Date: Mon, 4 Jan 2021 12:15:18 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
 Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <1BC8BF20-B961-4360-855B-5BB95338BB8A@newclarity.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Spam_score: -2.9
X-Spam_score_int: -28
X-Spam_bar: --
X-Spam_report: Spam detection software, running on the system "scanner01.home", has
 identified this incoming email as possible spam.  The original message
 has been attached to this so you can view it (if it isn't spam) or label
 similar future email.  If you have any questions, see
 the administrator of that system for details.
 
 Content preview:  Hi, On 03.01.21 12:01, Mike Schinkel wrote: > So in my perfect
    world this: > > enum BookingStatus { > case PENDING; > case CONFIRMED; >
   case CANCELLED; > } > > Would be equivalent to: > > enum BookingStatus { >
    case PENDING = "PENDING"; > case CONFIRMED = "CONFIRMED"; > case CANCELLED
    = "CANCELLED"; > } [...] 
 
 Content analysis details:   (-2.9 points, 5.0 required)
 
  pts rule name              description
 ---- ---------------------- --------------------------------------------------
 -1.0 ALL_TRUSTED            Passed through trusted hosts only via SMTP
 -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
                             [score: 0.0000]
  0.0 URIBL_BLOCKED          ADMINISTRATOR NOTICE: The query to URIBL was blocked.
                             See
                             http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
                              for more information.
                             [URIs: externals.io]
 -0.0 NICE_REPLY_A           Looks like a legit reply (A)
X-CMAE-Envelope: MS4wfF+2DOLBuuB7N70s63pL/mnpNhdgJ08kZPG7Ytj5JhZArLm9vkyldAN5Obi1ZroCzr1aPYC3ru4yhVPGVfBPTA68hpzreYl36O1SYx4XyDknGl5wK8NF
 5Ml68W4iLCjtKGe3nv9reqOY6adAOB92Yz5voWRNDZyG3/vPHoDh5aZq
Subject: Re: [PHP-DEV] [RFC] Enumerations, Round 2
From: markus@fischer.name (Markus Fischer)

Hi,

On 03.01.21 12:01, Mike Schinkel wrote:
> So in my perfect world this:
> 
> enum BookingStatus {
>       case PENDING;
>       case CONFIRMED;
>       case CANCELLED;
> }
> 
> Would be equivalent to:
> 
> enum BookingStatus {
>       case PENDING = "PENDING";
>       case CONFIRMED = "CONFIRMED";
>       case CANCELLED = "CANCELLED";
> }

I'm with Mikes' suggesting here, see also my previous messages [1] [2].

I don't know how to back this up with numbers, but the way I see it the 
majority of use cases will have a benefit of being able to directly use 
the literal values derived from the lexical ones and the ability to have 
custom values is feature next to it.

[1] https://externals.io/message/112626#112655
[2] https://externals.io/message/112626#112663