4 ms·
I read the README but I'm not understanding yet why the return path might be what you want. The stack trace at error creation sounds more useful.
by da39a3ee 3y ago
I read the README but I'm not understanding yet why the return path might be what you want. The stack trace at error creation sounds more useful.
- prashantv 3y agoThe stack trace and return path are pretty similar if the flow goes through function calls on a single goroutine, but if errors propagate across goroutines or across different stacks (E.g., via channels), then it can miss some useful details. Here's an example that compares them: https://pkg.go.dev/braces.dev/errtrace#readme-comparison-with-stack-traces https://pkg.go.dev/braces.dev/errtrace#readme-comparison-wit... Since the HTTP library uses a separate goroutine to create connections, the stack trace at creation time doesn't have details about the user request that triggered the connection.