Description
This is a tracking issue for the RFC "Fix the Error trait" (rust-lang/rfcs#2504).
Steps:
- Implement the RFC (cc @rust-lang/libs)
-
sourcemethod Add Error::source method per RFC 2504. #53533 - Backtrace API std: Add a
backtracemodule #64154
-
-
Implement proof of concept showing stabilizingbacktracemethod won't prevent movingErrorintocorelater Start working on proof of concept for exposing Backtrace in core #77384 - Fix std::backtrace::Backtrace's fmt representations
Precision flag support Formatting of std::backtrace::Backtrace #65280this is non-blocking for stabilization- Differences with
panic!backtraces Backtrace rendering inconsistent betweenstd::backtraceand panics #71706
- Adjust documentation (see instructions on forge)
- Stabilization PR (see instructions on forge)
Unresolved questions:
- The choice to implement nullability internal to backtrace may prove to be a mistake: during the period when backtrace APIs are only available on nightly, we will gain more experience and possible change backtrace's constructors to return an
Option<Backtrace>instead.
Current status:
Metadata
Metadata
Assignees
Labels
Area: Error handlingBlocker: Approved by a merged RFC but not yet implemented.Category: An issue tracking the progress of sth. like the implementation of an RFCLibs issues that are tracked on the team's project board.Project group: Error handling (https://github.com/rust-lang/project-error-handling)Relevant to the library API team, which will review and decide on the PR/issue.