Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128250
Precedence: bulk
MIME-Version: 1.0
Date: Mon, 28 Jul 2025 12:17:05 +0200
To: Dmitry Derepko <xepozzd@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] [DISCUSSION] User-land Throwable
In-Reply-To: <CANTuiHvOSimVNPpDxVE5KE8AW63HZmC5=kuSy_uRy_nJRgS9+w@mail.gmail.com>
References: <CANTuiHvOSimVNPpDxVE5KE8AW63HZmC5=kuSy_uRy_nJRgS9+w@mail.gmail.com>
Message-ID: <73a35675dff31a1eaf76b67af567194e@bastelstu.be>
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

Am 2025-07-28 11:41, schrieb Dmitry Derepko:
> A few years ago I found that a library printed error traces wrong.
> After a little research I found that there was a mix of 3rd party
> integration error + raised error around the current bridge 
> implementation
> (http client).
> 
> There were several PHP applications with microservices architecture 
> which I
> had access to (docker + sources).
> 
> So having the message and traces I'd like to have an error chain as it 
> can
> be done chaining several errors through a new Exception(previous: $e).
> But PHP does not allow you to manually implement Throwable. Instead you
> should extend Exception. But after that you still cannot override the
> getTrace() method because it's final.
> 
> So my proposal is pretty simple: Remove both restrictions.

I'm afraid I don't quite understand what actual goal you intend to solve 
with the proposal. The description of your use case is very abstract, 
can you provide a real-world example of a use-case you want to enable?

Best regards
Tim Düsterhus