Hi @kevkevinpal Please review this PR.

Hmm I'm not sure this is exactly what were looking for since this gets the variables from the panic/error message.

I was thinking maybe there is a way to get the variable state from the stacktrace without having to pass the variable explicitly to the error

not sure if that makes sense?

@kevkevinpal :
The approach you're suggesting - getting variable values directly from the stack trace without explicitly passing them - isn't possible in Go by design. Here's why:

1- Go's stack traces only contain function names, file locations, and line numbers
2- Variable values are not preserved in the stack trace when a panic occurs
3- Go intentionally prevents access to variables from previous stack frames for memory safety

To capture variable state during errors, we would need to either:

• Add explicit logging/monitoring throughout the code
• Use a debugging tool like Delve
• Implement runtime hooks before the panic occurs

Would you like me to explore any of these alternative approaches instead?