Missing the stack traces on errors

Hi,

I'm using this library in a project and I kind of like the flow.
However I'm missing the stack traces when an a failure is reached.

Would love to have a way to capture the stack-trace on fail so to have an easier experience when debugging.
Is this feasible?

Thanks,
Euge

The issue names no files, tests, or entry points. Start by locating how failjure represents failures and where errors are created, then assess how stack traces could be captured and exposed without disrupting the existing flow. Done should be a defined, usable way to obtain stack traces when a failure occurs, with behavior covered by appropriate tests.

Written by the indexing model from the issue text.