Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127698
Precedence: bulk
MIME-Version: 1.0
Date: Tue, 17 Jun 2025 15:54:43 -0400
Message-ID: <CALdAX-2vK10a3wqL5A39v3RJ8_wLLz2N7sZARUhuSQpUAV95Uw@mail.gmail.com>
Subject: [PHP-DEV] Pre-RFC: dd() and dump() functions for PHP core
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary="00000000000074e71b0637c9e4f4"
From: braunson@gmail.com (Braunson Yager)

--00000000000074e71b0637c9e4f4
Content-Type: text/plain; charset="UTF-8"

Hi internals,

I'd like to gauge interest in adding two debugging functions to PHP core:
dd() and dump().

*Background*
Currently, developers rely on userland solutions like Laravel's dd() helper
or Symfony's VarDumper for enhanced debugging output. These tools are
widely adopted across the PHP ecosystem, suggesting strong demand for
better debugging primitives.


*Proposal Overview*- dd($var, ...$vars) - "dump and die" - outputs
formatted debug info and terminates execution
- dump($var, ...$vars) - outputs formatted debug info and continues
execution


*Enhanced Features Over Existing Solutions*- Native performance (no
userland overhead)
- Stack trace integration
- Memory usage reporting
- Execution timing (potentially)
- Better CLI formatting


*Why Core vs Userland?*Similar to how var_dump() provides basic
introspection, these functions would offer enhanced debugging capabilities
that benefit the entire ecosystem, not just framework users.

*Implementation*
I'm seeking collaboration with an experienced PHP core developer for the C
implementation. I can handle the RFC documentation, testing, etc. I have
experience with the Laravel/Symfony codebases.


*Before drafting a formal RFC, I'd appreciate feedback on:*1. General
appetite for enhanced debugging functions in core
2. Concerns about naming conflicts with existing userland helpers
3. Preferred feature scope

Thoughts?

Best regards,
Braunson Yager

--00000000000074e71b0637c9e4f4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">Hi inte=
rnals,<br><br>I&#39;d like to gauge interest in adding two debugging functi=
ons to PHP core: dd() and dump().<br></div><div><br></div><b>Background</b>=
<br><div dir=3D"ltr">Currently, developers rely on userland solutions like =
Laravel&#39;s dd() helper or Symfony&#39;s VarDumper for enhanced debugging=
 output. These tools are widely adopted across the PHP ecosystem, suggestin=
g strong demand for better debugging primitives.<br><br><b>Proposal Overvie=
w<br></b>- dd($var, ...$vars) - &quot;dump and die&quot; - outputs formatte=
d debug info and terminates execution<br>- dump($var, ...$vars) - outputs f=
ormatted debug info and continues execution<br><br><b>Enhanced Features Ove=
r Existing Solutions<br></b>- Native performance (no userland overhead)<br>=
- Stack trace integration<br>- Memory usage reporting<br>- Execution timing=
 (potentially)<br>- Better CLI formatting<br><br><b>Why Core vs Userland?<b=
r></b>Similar to how var_dump() provides basic introspection, these functio=
ns would offer enhanced debugging capabilities that benefit the entire ecos=
ystem, not just framework users.<br><br><b>Implementation</b><br>I&#39;m se=
eking collaboration with an experienced PHP core developer for the C implem=
entation. I can handle the RFC documentation, testing, etc.=C2=A0I have exp=
erience with the Laravel/Symfony codebases.<br><br><b>Before drafting a for=
mal RFC, I&#39;d appreciate feedback on:<br></b>1. General appetite for enh=
anced debugging functions in core<br>2. Concerns about naming conflicts wit=
h existing userland helpers<br>3. Preferred feature scope<br><br>Thoughts?<=
br><br>Best regards,<br>Braunson Yager</div>
</div>
</div>
</div>

--00000000000074e71b0637c9e4f4--