Tracking issue for RFC 2504, "Fix the Error trait"

[Centril]

This is a tracking issue for the RFC "Fix the Error trait" (rust-lang/rfcs#2504).

Steps:

• Implement the RFC (cc @rust-lang/libs)
  • source method Add Error::source method per RFC 2504. #53533
  • Backtrace API std: Add a backtrace module #64154
• Implement proof of concept showing stabilizing backtrace method won't prevent moving Error into core later 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 #65280 this is non-blocking for stabilization
  • Differences with panic! backtraces Backtrace rendering inconsistent between std::backtrace and 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:

#53487 (comment)

[L-as]

What parts haven't been implemented?

[withoutboats]

I've updated the tracking issue to reflect that, but right now the source method has been implemented, but the backtrace related APIs have not been implemented

[L-as]

Perhaps I could try implementing this, is it OK to just use the backtrace crate?

[alexcrichton]

Implementing backtraces in the standard library will probably not use the backtrace crate but rather the backtrace API that's already in the standard library for RUST_BACKTRACE. We can perhaps unify these implementations in the long run, but for now it's infeasible to do so.

The current platform-independent backtrace code lives here, mostly in the _print function. Implementing the API defined in the RFC will likely involve reusing these interfaces to define a struct which carries along the relevant information.

@laaas if you'd like to implement this please feel free! Also feel free to reach out with any questions.

[L-as]

Thanks! Will definitely try implementing it.

[frewsxcv]

Thanks! Will definitely try implementing it.

@laaas Did you make any progress? Need any help?

[L-as]

@frewsxcv Actually not!

I haven't really looked at it much, so if you want to work on it, go ahead!