[PHP-DEV] Re: [RFC] [Discussion] Literal Scalar Types
Seifeddine Gmati <[email protected]> Thu, 23 Jul 2026 06:47:45 +0100
| Newsgroups | gmane.comp.php.devel |
|---|---|
| Message-ID | <CAFyg4HikAC19+pJuskd1w-rsWdfJMm3jG_x90mJwATSPWxAHMA@mail.gmail.com> |
--0000000000003a46ea065740cc71 Content-Type: text/plain; charset="UTF-8" On Thu, 23 Jul 2026 at 06:13, Seifeddine Gmati <[email protected]> wrote: > Subject: Re: [RFC] Literal Scalar Types > On Mon, 15 Jun 2026 at 02:22, Seifeddine Gmati <[email protected]> > wrote: > >> Hello Internals, >> >> I'd like to start the discussion on a new RFC adding literal scalar >> types to PHP. >> >> - RFC: https://wiki.php.net/rfc/literal_scalar_types >> - Implementation: https://github.com/php/php-src/pull/22314 >> >> Thanks, >> Seifeddine. >> > > Hi internals, > > I have updated the Literal Scalar Types RFC to version 1.0, which I > consider the final revision: https://wiki.php.net/rfc/literal_scalar_types > > The changes are editorial, based on feedback in this thread. I merged the > "Accepted literal syntax" section into the per-type sections so each > literal kind is described in one place, added a paragraph to the > introduction on where literal types fit next to enums, tightened the > reasoning in the matching semantics section, and added a short note on enum > comparisons to the Performance section. The proposal itself is unchanged: > the syntax, the semantics and the three votes are the same as in 0.3. > > Since this is a minor revision, I am opening voting shortly. A separate > [VOTE] thread will follow. > > Thanks to everyone who took part in the discussion. > > Seifeddine > Hello internals, A procedural update, following my retraction in the [VOTE] thread. Earlier I opened voting on this RFC without meeting the prerequisites: no Intent to Vote had been posted two days in advance, and the 1.0 update I announced earlier is a Minor change, which starts a seven-day Cooldown Period. I retracted the vote. The widgets are closed, and the RFC is back to Under Discussion. The text is unchanged since the 1.0 announcement and I intend to keep it frozen until the vote. Please consider this message my formal Intent to Vote. The Cooldown Period ends on July 30, and I plan to reopen the vote that morning (UTC), running for the standard fourteen days within the Intent to Vote lifetime. One open question is the PHP 8.6 feature freeze. A vote opened on July 30 closes on August 13, the day of beta1, and the tag is created on August 11, so a merge would happen during the beta period and needs Release Manager approval. I am checking with the 8.6 RMs whether that is acceptable. If it is not, I will retarget the RFC to PHP 8.7 (or 9.0?) instead. Retargeting changes the voting widgets, so it would be announced here as a change, trigger its own Cooldown Period, and be followed by a fresh Intent to Vote, with no deadline pressure. Thanks for your patience. Seifeddine. --0000000000003a46ea065740cc71 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr">On Thu, 23 Jul 2026 at 06:13, Seifeddine = Gmati <[email protected]> wrote:</div><div class=3D"gmail_quot= e gmail_quote_container"><blockquote class=3D"gmail_quote" style=3D"margin:= 0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">= <div dir=3D"ltr"><div dir=3D"ltr">Subject: Re: [RFC] Literal Scalar Types<b= r>On Mon, 15 Jun 2026 at 02:22, Seifeddine Gmati <[email protected]= re> wrote:</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_qu= ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20= 4);padding-left:1ex">Hello Internals,<br> <br> I'd like to start the discussion on a new RFC adding literal scalar<br> types to PHP.<br> <br> - RFC: <a href=3D"https://wiki.php.net/rfc/literal_scalar_types" rel=3D"nor= eferrer" target=3D"_blank">https://wiki.php.net/rfc/literal_scalar_types</a= ><br> - Implementation: <a href=3D"https://github.com/php/php-src/pull/22314" rel= =3D"noreferrer" target=3D"_blank">https://github.com/php/php-src/pull/22314= </a><br> <br> Thanks,<br> Seifeddine.<br></blockquote><div><br></div><div>Hi internals,<br><br>I have= updated the Literal Scalar Types RFC to=20 version 1.0, which I consider the final revision:=20 <a href=3D"https://wiki.php.net/rfc/literal_scalar_types" target=3D"_blank"= >https://wiki.php.net/rfc/literal_scalar_types</a><br><br>The changes are= =20 editorial, based on feedback in this thread. I merged the "Accepted=20 literal syntax" section into the per-type sections so each literal kin= d=20 is described in one place, added a paragraph to the introduction on=20 where literal types fit next to enums, tightened the reasoning in the=20 matching semantics section, and added a short note on enum comparisons=20 to the Performance section. The proposal itself is unchanged: the=20 syntax, the semantics and the three votes are the same as in 0.3.<br><br>Si= nce this is a minor revision, I am opening voting shortly. A separate [VOTE= ] thread will follow.<br><br>Thanks to everyone who took part in the discus= sion.<br><br>Seifeddine=C2=A0</div></div></div></blockquote><div><br></div>= <div>Hello internals,<br><br>A procedural update, following my retraction i= n the [VOTE] thread.<br><br>Earlier I opened voting on this RFC without mee= ting the prerequisites: no Intent to Vote had been posted two days in advan= ce, and the 1.0 update I announced earlier is a Minor change, which starts = a seven-day Cooldown Period. I retracted the vote. The widgets are closed, = and the RFC is back to Under Discussion. The text is unchanged since the 1.= 0 announcement and I intend to keep it frozen until the vote.<br><br>Please= consider this message my formal Intent to Vote. The Cooldown Period ends o= n July 30, and I plan to reopen the vote that morning (UTC), running for th= e standard fourteen days within the Intent to Vote lifetime.<br><br>One ope= n question is the PHP 8.6 feature freeze. A vote opened on July 30 closes o= n August 13, the day of beta1, and the tag is created on August 11, so a me= rge would happen during the beta period and needs Release Manager approval.= I am checking with the 8.6 RMs whether that is acceptable. If it is not, I= will retarget the RFC to PHP 8.7 (or 9.0?) instead. Retargeting changes th= e voting widgets, so it would be announced here as a change, trigger its ow= n Cooldown Period, and be followed by a fresh Intent to Vote, with no deadl= ine pressure.<br><br>Thanks for your patience.<br><br>Seifeddine.</div></di= v></div> --0000000000003a46ea065740cc71--