Hey Ilija! On Thu, 19 Jan 2023, 20:26 Ilija Tovilo, <[email protected]> wrote:
> However, as demonstrated by the 3v4l, it's not > exactly trivial. It also requires the full stack trace, as well as all > frame objects and arguments. That's not going to be great for > performance. So saying debug_backtrace() exists for this purpose is > misleading, to say the least. > Meh, I made the kinkiest code work that way, and it's mostly for edge cases: I would raise this as a problem once: 1. The use-case is not kinky 2. The performance benefits are so large that they warrant a language change Integration-testing code that uses `debug_backtrace()` is usually sufficient for making this stuff work. >
