Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112479
Message-ID: <2A21EBAE-85A6-46BB-8261-357A29756DD9@newclarity.net>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_F446950B-8640-4367-8ABE-0F2768E55040"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Wed, 9 Dec 2020 15:44:14 -0500
In-Reply-To: <CAG9XoMSD2L3MqAF3wcazjwEsj1yYsMfJ7-04GLEmscDXcsjdvw@mail.gmail.com>
Cc: Larry Garfield <larry@garfieldtech.com>,
 php internals <internals@lists.php.net>
To: Benjamin Morel <benjamin.morel@gmail.com>
References: <d1c4689e-9120-4e90-837c-a1b3eac63cd6@www.fastmail.com>
 <DA260CE1-8523-4737-A5CE-052160846E79@newclarity.net>
 <CAG9XoMSD2L3MqAF3wcazjwEsj1yYsMfJ7-04GLEmscDXcsjdvw@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Enumerations
From: mike@newclarity.net (Mike Schinkel)

--Apple-Mail=_F446950B-8640-4367-8ABE-0F2768E55040
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> On Dec 9, 2020, at 3:29 PM, Benjamin Morel <benjamin.morel@gmail.com> =
wrote:
>=20
> On Wed, 9 Dec 2020 at 19:48, Mike Schinkel <mike@newclarity.net =
<mailto:mike@newclarity.net>> wrote:
>=20
> 5. Someone else mentioned shortcut syntax, which I would like to =
mention again, although I realize implement details might make this a =
non-starter. =20
>=20
> So if I have a function that accepts a Size from above, e.g.:
>=20
> function show(Size $size) {}
>=20
> Then it would be great if we could call the function like this since =
its parameter was type-hinted:
>=20
> show(::Medium)=20
>=20
> Rather than always having to write:
>=20
> show(Size::Medium)=20
>=20
> So can we consider a shortcut syntax?
>=20
> I'm not sure what value a shortcut syntax would bring, but it would =
surely break, or at least make ambiguous, union types:
>=20
>     function show(Enum1|Enum2 $value)  {}
>     show(::Medium)
>=20
> Which enum would Medium resolve to?

Good question. =20

What *could* happen is:

1. It could resolve to the Enum that has a ::Medium,=20

2. Or it could be disallowed for union type hints (probably the better =
option as adding a "Medium" to the other enum could inadvertently break =
code that calls it.)

3. This suggestion could just be tabled.


Again, I am just asking if this is something we could consider because =
it would be nice to shorten line length in cases where expressions get =
really long.


Maybe a different question could be if a "use" statement could empower =
making explicit shorthands/aliases?


-Mike

P.S. I completely understand if either of these things are out of scope =
for this RFC.


--Apple-Mail=_F446950B-8640-4367-8ABE-0F2768E55040--