Tracking Issue for backtrace_frames · Issue #79676 · rust-lang/rust (original) (raw)

This is a tracking issue for one of the features mentioned in #81022, the ability to create an iterator over backtrace frames.
The feature gate for the issue is #![feature(backtrace_frames)].

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

Steps

• Implement the capability to return an iterator over the Backtrace type
• Adjust documentation (see instructions on rustc-dev-guide)
• Stabilization PR (see instructions on rustc-dev-guide)

Unresolved Questions

• We're opting to not derive Clone on the Backtrace type so as not to expose a public Backtrace::clone method. Private clone methods are implemented instead. Is this the long-term API we'll want to stick with?
• We'll want to think about the FromIterator implementation a bit more, because we can't mark trait implementations as unstable so if we added one to Backtrace we'd be committing to it right away.

Implementation history

• Add Frames Iterator for Backtrace #81022 adds a frames method on the Backtrace type that returns a Vec<BacktraceFrame> that can be iterated over.