Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129718
Precedence: list
MIME-Version: 1.0
References: <CAEKnhAEO8w0GJXTVyH_nwK8nGQGdJcNNkGOPMnYDVrcsNGrm4A@mail.gmail.com>
In-Reply-To: <CAEKnhAEO8w0GJXTVyH_nwK8nGQGdJcNNkGOPMnYDVrcsNGrm4A@mail.gmail.com>
Date: Mon, 29 Dec 2025 19:52:44 +0100
Message-ID: <CAEKnhAE5iG6VfgS6=+FrpbDN5T-7iOA7j0gN9n-pr0HmBe=3EA@mail.gmail.com>
Subject: [PHP-DEV] Re: [RFC] Stream Error Handling Improvements
To: PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000004065eb06471bc084"
From: bukka@php.net (Jakub Zelenka)

--0000000000004065eb06471bc084
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 18, 2025 at 7:38=E2=80=AFPM Jakub Zelenka <bukka@php.net> wrote=
:

> Hello,
>
> I would like to introduce a new stream error handling RFC that is part of
> my stream evolution work (PHP Foundation project funded by Sovereign Tech
> Fund) :
>
> https://wiki.php.net/rfc/stream_errors
>
>
 Hi, I just published version 2.0 which is a significant redesign including=
:

- Introducing StreamErrorStore, StreamErrorMode and StreamErrorCode enums
(the code also includes various suggested helper methods). The code is
backed (int) because I need to keep the number to easily match the category
and simplify the mapping. I think that in this case a backed enum is better=
.

- The error data are now in a StreamError class instead of an associative
array. This also simplifies StreamException which now has just a single
method to return the StreamError instance. The error handler callback
signature was also simplified to take just a single StreamError parameter
instead of multiple individual parameters.

- Errors are now grouped per operation and reported at the end of the call.
This also supports nested calls (e.g. in user streams) so they don't
overlap. And it delays the execution of error handlers (not just the stream
error callback but also the usual error handler if default standard error
triggering is used) which should be safer as noted by Arnaud.

- The storing of errors is done at the end of the operation grouping and
contains only the last grouped errors. So the function name was changed to
stream_get_last_error(). It returns just a single StreamError which has a
next property pointing to the next error if there is any.

- Stream is no longer exposed and errors are not collected on streams but
globally in the same way as wrappers. It is actually no longer even
collected per wrapper because it doesn't make much sense when the errors
are grouped per operation.

- Terminal (and NonTerminal) was renamed to Terminating (and
NonTerminating).

- Invalid enum types for context options (error_mode and error_store) now
throw TypeError.

- Implemented operation pooling to minimize memory allocations during error
handling (pre-allocated pool for up to 8 nested operations).

I hope this addresses all concerns.

Kind regards,

Jakub

--0000000000004065eb06471bc084
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Nov 18, 2025 at 7:38=E2=80=AFPM J=
akub Zelenka &lt;<a href=3D"mailto:bukka@php.net">bukka@php.net</a>&gt; wro=
te:</div><div class=3D"gmail_quote gmail_quote_container"><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div dir=3D"ltr">Hello,<br><br>I would lik=
e to introduce a new stream error handling RFC that is part of my stream ev=
olution work (PHP Foundation project funded by Sovereign Tech Fund) :<br><b=
r><a href=3D"https://wiki.php.net/rfc/stream_errors" target=3D"_blank">http=
s://wiki.php.net/rfc/stream_errors</a><br><div><br></div></div></blockquote=
><div><br></div><div>=C2=A0Hi, I just published version 2.0 which is a sign=
ificant redesign including:</div><br>- Introducing StreamErrorStore, Stream=
ErrorMode and StreamErrorCode enums (the code also includes various suggest=
ed helper methods). The code is backed (int) because I need to keep the num=
ber to easily match the category and simplify the mapping. I think that in =
this case a backed enum is better.<br><br></div><div class=3D"gmail_quote g=
mail_quote_container">- The error data are now in a StreamError class inste=
ad of an associative array. This also simplifies StreamException which now =
has just a single method to return the StreamError instance. The error hand=
ler callback signature was also simplified to take just a single StreamErro=
r parameter instead of multiple individual parameters.<br><br></div><div cl=
ass=3D"gmail_quote gmail_quote_container">- Errors are now grouped per oper=
ation and reported at the end of the call. This also supports nested calls =
(e.g. in user streams) so they don&#39;t overlap. And it delays the executi=
on of error handlers (not just the stream error callback but also the usual=
 error handler if default standard error triggering is used) which should b=
e safer as noted by Arnaud.<br><br></div><div class=3D"gmail_quote gmail_qu=
ote_container">- The storing of errors is done at the end of the operation =
grouping and contains only the last grouped errors. So the function name wa=
s changed to stream_get_last_error(). It returns just a single StreamError =
which has a next property pointing to the next error if there is any.<br><b=
r></div><div class=3D"gmail_quote gmail_quote_container">- Stream is no lon=
ger exposed and errors are not collected on streams but globally in the sam=
e way as wrappers. It is actually no longer even collected per wrapper beca=
use it doesn&#39;t make much sense when the errors are grouped per operatio=
n.<br><br></div><div class=3D"gmail_quote gmail_quote_container">- Terminal=
 (and NonTerminal) was renamed to Terminating (and NonTerminating).<br><br>=
</div><div class=3D"gmail_quote gmail_quote_container">- Invalid enum types=
 for context options (error_mode and error_store) now throw TypeError.<br><=
br></div><div class=3D"gmail_quote gmail_quote_container">- Implemented ope=
ration pooling to minimize memory allocations during error handling (pre-al=
located pool for up to 8 nested operations).</div><div class=3D"gmail_quote=
 gmail_quote_container"><br></div><div class=3D"gmail_quote gmail_quote_con=
tainer">I hope this addresses all concerns.<br><br>Kind regards,</div><div =
class=3D"gmail_quote gmail_quote_container"><br>Jakub<div><br></div></div><=
/div>

--0000000000004065eb06471bc084--