Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112697
To: internals@lists.php.net
References: <eadd4a32-a05b-463b-a91f-a5d353c577b2@www.fastmail.com>
 <012f426d-ff07-fce7-d642-c64bafa5aaf5@gmail.com>
 <f3c8e38a-faba-48db-95e2-87f4c19ebe12@www.fastmail.com>
Message-ID: <30d81afa-f7f1-97fa-123c-1d131d5113ee@gmail.com>
Date: Thu, 31 Dec 2020 12:46:27 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <f3c8e38a-faba-48db-95e2-87f4c19ebe12@www.fastmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] [RFC] Enumerations, Round 2
From: rowan.collins@gmail.com (Rowan Tommins)

On 30/12/2020 19:47, Larry Garfield wrote:
> That's partially left over from when we had per-case methods, where grouping would be highly fugly.  However, I'm still advocating for tagged unions (in a future step) having per-case methods, and that would make the grouping syntax fugly again.  It's trivial to add later, so for now I think it's best to skip.  If we find later on it doesn't get in the way of anything it's an easy addition.


Yes, that had occurred to me. Just to reiterate, though, the original 
justification read "it is unclear how common [cases without block 
definitions] will be in practice"; with the current implementation, we 
know for a fact that it will be extremely common - even if tagged unions 
use overlapping syntax that doesn't group nicely, every "unit enum" will 
have cases with no blocks.

Still, it's not a big deal either way, and as you say can easily be 
added later.

Regards,

-- 
Rowan Tommins
[IMSoP]