You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ever since RUST_BACKTRACE got split up into a short and full backtrace, there used to be a message that tells you about the full backtrace when you are seeing the shortened one. The message however only comes up when stack frames are omitted See here. This used to be the case for the shortened backtrace, but since the frame pruning logic got reverted by #41364, this message is now dead code until frame pruning is implemented again (#40264). However it might also make sense to just always show this message for a short backtrace instead of counting the amount of omitted frames.
The text was updated successfully, but these errors were encountered:
If no frames are omitted, then full and short backtraces are equivalent.
No reason to spend people's time and recommend using full if the result will be the same.
Ever since RUST_BACKTRACE got split up into a short and full backtrace, there used to be a message that tells you about the full backtrace when you are seeing the shortened one. The message however only comes up when stack frames are omitted See here. This used to be the case for the shortened backtrace, but since the frame pruning logic got reverted by #41364, this message is now dead code until frame pruning is implemented again (#40264). However it might also make sense to just always show this message for a short backtrace instead of counting the amount of omitted frames.
The text was updated successfully, but these errors were encountered: