# Project Group Error Handling Meeting 2021-09-27 ###### tags: `Error Handling` `Minutes` **Attendees**: ... ## Agenda Items - [Open action items](https://hackmd.io/@rust-libs/Hyj7kRSld) - Triage - Individual Status Updates ## Triage ### Nominated None ### PG Error Handling - [5 `rust-lang/rust` `PG-error-handling` items](https://github.com/rust-lang/rust/issues?q=label:PG-error-handling+is:open) - [[53487](https://github.com/rust-lang/rust/issues/53487)] *Tracking issue for RFC 2504, "Fix the Error trait"* - Still blocked on resolving backtrace questions - Current plan to resolve involves landing generic member access on nightly and then removing the backtrace method from the error trait in favor of Generic member access - Once that's done we will need to finish implementing the negative trait coherence PR and probably a few others to finally let us move Error into core - [[58520](https://github.com/rust-lang/rust/issues/58520)] *Tracking issue for error source iterators* - unassigned - [[65280](https://github.com/rust-lang/rust/issues/65280)] *Formatting of std::backtrace::Backtrace* - unassigned - [[72981](https://github.com/rust-lang/rust/pull/72981)] *Stabilize the backtrace feature.* - see "Fix the Error trait" issue - [[77474](https://github.com/rust-lang/rust/issues/77474)] *Add #\[track\_caller\] support to \`?\`* - We may want to prioritize this a bit more. Currently there is a tension between performance with the `std::result::Result` type and fidelity in error reporting available by default ### Area Error Handling **Note**: I'm going to be going through and tagging the issues from this section that are relevant to us with our project group tag and remove the irrelevant ones from the agenda. - [14 `rust-lang/rust` `A-error-handling` items](https://github.com/rust-lang/rust/issues?q=label:A-error-handling+is:open) - [[44838](https://github.com/rust-lang/rust/issues/44838)] *Tracking issue for RFC 2011: nicer assert messages* - [[54889](https://github.com/rust-lang/rust/issues/54889)] *Implement Try for ExitStatus* - [[60784](https://github.com/rust-lang/rust/issues/60784)] *Tracking issue for stabilizing \`Error::type\_id\`* - [[66745](https://github.com/rust-lang/rust/issues/66745)] *Tracking issue for PanicInfo::message* - [[77384](https://github.com/rust-lang/rust/pull/77384)] *Start working on proof of concept for exposing Backtrace in core* - [[79085](https://github.com/rust-lang/rust/pull/79085)] *Add Backtrace::set\_enabled to override environment variables* - [[79676](https://github.com/rust-lang/rust/issues/79676)] *Tracking Issue for \`backtrace\_frames\`* - [[80190](https://github.com/rust-lang/rust/issues/80190)] *API: Add \`err\_or\` and \`err\_or\_else\` to \`Option\`* - closed this one since nobody replied when we asked for concrete use cases - [[84908](https://github.com/rust-lang/rust/issues/84908)] *Tracking Issue for ExitStatusError* - [[86826](https://github.com/rust-lang/rust/pull/86826)] *\[draft\] Store the path in io::Error without extra allocations.* - [[87869](https://github.com/rust-lang/rust/pull/87869)] *Make io::Error use 64 bits on targets with 64 bit pointers.* ### PG Error Handling None ## Actions - [ ] Reply to all issues/PRs discussed in this meeting, or add them to the [open action items](https://hackmd.io/UrERZvi5RwyxfGvo-RtC6g). _Generated by [fully-automatic-rust-libs-team-triage-meeting-agenda-generator](https://github.com/rust-lang/libs-team/tree/main/tools/agenda-generator)_