> <@kares:matrix.org> also had another (minor) discussion topic as I was looking into `rescue nil` and friends : 
> does it make sense for a provided back-trace (non-empty or nil) to still capture a stack-trace? 
> ... case like `raise SomeError, 'failed', ex.backtrace`
> 
> currently I do see a value in logging the 'captured' trace (-Xlog.backtraces) but since its provided I am not sure its to be expected

headius: its not about cause ... its that these two cases behave differently:

`raise SomeError, 'failed', some_backtrace`
`raise SomeError, 'failed', []`

first is slow since it will capture the stack-trace while the second won't.
besides having proper traces on where that ex was generated in the log the captured backtrace is than not used since its provided. so I wasn't sure if this is by design or we should also improve the first case to be not generating a stack-trace ...