-
Notifications
You must be signed in to change notification settings - Fork 114
Open
Labels
area/libsRelates to first-party libraries/crates/packages (area)Relates to first-party libraries/crates/packages (area)area/libs > error-stackAffects the `error-stack` crate (library)Affects the `error-stack` crate (library)category/enhancementNew feature or requestNew feature or requestlang/rustPull requests that update Rust codePull requests that update Rust code
Description
Related Problem
I looked through issues in case there was already a discussion about it, but didn't manage to find anything - please point me to it if there was one.
Currently, the printed report looks something like this
external error
├╴at src/main.rs:29:20
│
├─▶ intermediate error
│ ╰╴at src/main.rs:21:21
│
╰─▶ internal error
╰╴at src/main.rs:13:23
This seems a bit confusing from the design perspective - it implies that there is some data flow going on from the external error to internal ones.
Proposed Solution
I wonder, wouldn't it be more intuitive if it looked something like this:
external error
╰╴at src/main.rs:29:20
▲
└── intermediate error
┌─▶ ╰╴at src/main.rs:21:21
│
╰── internal error
╰╴at src/main.rs:13:23
or this:
external error
╰╴at src/main.rs:29:20
▲
└── intermediate error
▲ ╰╴at src/main.rs:21:21
│
╰── internal error
╰╴at src/main.rs:13:23
Alternatives
No response
Additional context
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/libsRelates to first-party libraries/crates/packages (area)Relates to first-party libraries/crates/packages (area)area/libs > error-stackAffects the `error-stack` crate (library)Affects the `error-stack` crate (library)category/enhancementNew feature or requestNew feature or requestlang/rustPull requests that update Rust codePull requests that update Rust code