Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111998
MIME-Version: 1.0
References: <CAFecBuBw1fg89N-ywCOtCi_ETaR=6BRCqNPbJMoUyQTU0u-dxQ@mail.gmail.com>
 <CAGgaK7J-S_Gw61PLm4-yLgHmc5QYrqUQ22j=vP8oE3RQXNeBJQ@mail.gmail.com>
In-Reply-To: <CAGgaK7J-S_Gw61PLm4-yLgHmc5QYrqUQ22j=vP8oE3RQXNeBJQ@mail.gmail.com>
Date: Mon, 5 Oct 2020 03:03:14 +0300
Message-ID: <CAFecBuDKxqUDaRU6Eq3pmz3MyJsMxa_DdQ8nnXOuvokJY1+yog@mail.gmail.com>
To: Max Semenik <maxsem.wiki@gmail.com>
Cc: Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000001bc84005b0e136ba"
Subject: Re: [PHP-DEV] Literal types RFC
From: bogdanungureanu21@gmail.com (Bogdan Ungureanu)

--0000000000001bc84005b0e136ba
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Yeah, kind of, the problem with enums from what I understood from the
current RFCs is that you'll need extra code to map a scalar to that
specific enum value.

Besides that, a literal type implementation is afaik simpler to
implement/spec than enums, thus having a better chance to pass voting.

On Mon, Oct 5, 2020 at 2:56 AM Max Semenik <maxsem.wiki@gmail.com> wrote:

> =D0=BF=D0=BD, 5 =D0=BE=D0=BA=D1=82. 2020 =D0=B3., 02:38 Bogdan Ungureanu =
<bogdanungureanu21@gmail.com>:
>
>>
>> function getStatus(): "draft" | "published" { }
>>
>
> It sounds that what you're really asking for is enums, e.g.
>
> enum Status {
>     Draft,
>     Published
> };
>
> function getStatus(): Status { ... }
>
>>

--0000000000001bc84005b0e136ba--