Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127423
Precedence: bulk
MIME-Version: 1.0
Date: Thu, 22 May 2025 12:24:48 +0300
Message-ID: <CANTuiHuOxuwB2oTvPNekdkUCJbxWHMMrXjzQfHo2Tsui6NyoXw@mail.gmail.com>
Subject: [PHP-DEV] RFC: Single-Expression functions
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000043ff220635b60e8d"
From: xepozzd@gmail.com (Dmitry Derepko)

--00000000000043ff220635b60e8d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi, Internals!

I hope this message finds you well. I would like to respectfully propose
single-expression functions for PHP:
https://wiki.php.net/rfc/single-expression-functions

I've had extensive experience working with Kotlin, which offers a modern
approach to Java development and enables cleaner, more intuitive code.
Through this experience, I've encountered various concise syntax features,
and I believe one of them=E2=80=94single-expression functions=E2=80=94could=
 be a valuable
addition to PHP.

I'm aware that Larry Garfield previously proposed a similar feature several
years ago, though it unfortunately didn't pass the voting stage. I would
like to respectfully suggest that using "=3D" instead of "=3D>" to separate
declaration and implementation might be a better approach.

I believe this proposal aligns well with PHP's current modernization
efforts and the ongoing initiative to simplify various language constructs.
PHP has been consistently improving developer experience through features
like property promotion, arrow functions, the nullsafe operator,
getters/setters, and other syntax enhancements. This single-expression
function syntax would be a natural continuation of this trend, further
streamlining the developer workflow and making PHP more pleasant to write.

The primary motivation is to help streamline "data classes" by eliminating
the need for "{", "return", and "}", which can sometimes account for up to
30% of the code in such classes. This improvement would be particularly
timely as it directly enhances developer experience=E2=80=94a key focus of =
PHP's
recent evolution.

I would greatly appreciate your thoughts and feedback on this proposal, and
I'm looking forward to engaging in constructive discussion with the
community.

Thank you for your time and consideration.

---
Dmitriy Derepko

--00000000000043ff220635b60e8d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi, Internals!<br><br>I hope this message finds you well. =
I would like to respectfully propose single-expression functions for PHP: <=
a href=3D"https://wiki.php.net/rfc/single-expression-functions">https://wik=
i.php.net/rfc/single-expression-functions</a><br><br>I&#39;ve had extensive=
 experience working with Kotlin, which offers a modern approach to Java dev=
elopment and enables cleaner, more intuitive code. Through this experience,=
 I&#39;ve encountered various concise syntax features, and I believe one of=
 them=E2=80=94single-expression functions=E2=80=94could be a valuable addit=
ion to PHP.<br><br>I&#39;m aware that Larry Garfield previously proposed a =
similar feature several years ago, though it unfortunately didn&#39;t pass =
the voting stage. I would like to respectfully suggest that using &quot;=3D=
&quot; instead of &quot;=3D&gt;&quot; to separate declaration and implement=
ation might be a better approach.<br><br>I believe this proposal aligns wel=
l with PHP&#39;s current modernization efforts and the ongoing initiative t=
o simplify various language constructs. PHP has been consistently improving=
 developer experience through features like property promotion, arrow funct=
ions, the nullsafe operator, getters/setters, and other syntax enhancements=
. This single-expression function syntax would be a natural continuation of=
 this trend, further streamlining the developer workflow and making PHP mor=
e pleasant to write.<br><br>The primary motivation is to help streamline &q=
uot;data classes&quot; by eliminating the need for &quot;{&quot;, &quot;ret=
urn&quot;, and &quot;}&quot;, which can sometimes account for up to 30% of =
the code in such classes. This improvement would be particularly timely as =
it directly enhances developer experience=E2=80=94a key focus of PHP&#39;s =
recent evolution.<br><br>I would greatly appreciate your thoughts and feedb=
ack on this proposal, and I&#39;m looking forward to engaging in constructi=
ve discussion with the community.<br><br>Thank you for your time and consid=
eration.<br><br><div>---<br>Dmitriy Derepko</div></div>

--00000000000043ff220635b60e8d--