Open xuxife opened 8 months ago
An aside: I'm pretty sure CallerInfo isn't supposed to be exported. I've noted this in #1431.
How long is too long? Can you show us an example? In go 1.21 the Go runtime chose to only print the first and last 50 frames: https://tip.golang.org/doc/go1.21#runtime-changes We could emulate that.
An aside: I'm pretty sure CallerInfo isn't supposed to be exported. I've noted this in #1431.
I agree, but CallerInfo
appears to be heavily used in the wild: https://github.com/search?q=assert.CallerInfo%28%29+lang%3AGo+&type=code
Hi, I notice my assertion failure message sometimes has loooong stack traces, where most of them are from sdk or framework. I hope there could be a feature that I can customize
assert.CallerInfo()
, such that I can focus the stacks in my codebase.for instance, allow a package-level callback like
SkipCallerFrame(pc uintptr, file, line string) bool
to skip the frame if the callback returnstrue
.