Open target-san opened 5 months ago
My biggest concern is that I had to change TestCaseError
and TestError
types to keep backtrace. This effectively breaks public API. Unfortunately making this change cfg-conditional isn't very appealing too, as it introduces conditional matches in unit tests.
cc @matthew-russo
I had started going through this last night. will finish up later tonight
This effectively breaks public API.
Ah right, thank you for raising this. I don't think we can merge then until we move to a new major version unfortunately, or without making it a separate feature like you suggested, and yes I can see how that's unappealing.
Ok, then I guess the best course is to take out "backtrace"
feature and try introduce it as separate PR. Will do it in a few days.
we're looking at a 2.0 release so we can include this and a couple other things that are pending. it'd probably take 1-2 months to get everything together if those timelines work for you. also happy to accept changes with no backwards compatibility issues in the meantime if you want a faster turnaround
handle-panics
attempts to capture panic backtrace when one happens, instead of spitting it to consolebacktrace
enables actual backtraces usingstd::backtrace
Backtrace::frames()
andBacktraceFrame
are still experimental.P.S: Sorry for "PR spam", prev one #419 was closed prematurely due to accident
closes #356