Stack trace generation in Err() can be very costly

[flupke]

In an async heavy test (fuzzy testing with a lot of requests and network issues simulated with toxiproxy), rewriting a bit of the code with ts-results-es made the test fail.

I tracked the issue down to the stack trace generation in Err(), which was taking ~300ms parsing the source maps. I removed it entirely in this fork, which solved the issue.

I'm not sure how or if this should be fixed here, just wanted to report the issue.

[jstasiak]

Thank you for the report @flupke.

I'm wondering what needs to happen for stacktrace generation to take that long, I don't think it's normal.

In parallel I've been wondering how useful the stacktraces actually are there and I'm still not sure.

[flupke]

The sourcemaps are very large I guess :)