Support for tracing with Std::panic::Location (Feature Request) #142

Activity

1. Allen-Webb commented on Oct 6, 2021

   

   Allen-Webb

   on Oct 6, 2021

   More actions

   I also think some kind of backtrace chaining through source errors is really needed for thiserror.
2. 0xForerunner commented on Feb 11, 2023

   

   0xForerunner

   on Feb 11, 2023

   More actions

   Anyone know if there are plans to implement this? It looks like it should be pretty easy. A basic implementation looks like this

   // New error type encapsulating the original error and location data.
   #[derive(Debug, Clone)]
   struct LocatedError<E: Error + 'static> {
       inner: E,
       location: &'static Location<'static>,
   }
   
   impl<E: Error + 'static> Error for LocatedError<E> {
       fn source(&self) -> Option<&(dyn Error + 'static)> {
           Some(&self.inner)
       }
   }
   
   impl<E: Error + 'static> std::fmt::Display for LocatedError<E> {
       fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {
           write!(f, "{}, {}", self.inner, self.location)
       }
   }
   
   impl From<std::io::Error> for LocatedError<std::io::Error> {
       // The magic happens here
       #[track_caller]
       fn from(err: std::io::Error) -> Self {
           LocatedError {
               inner: err,
               location: std::panic::Location::caller(),
           }
       }
   }

   To me this feature is basically begging to be included in thiserror.

   👀React with 👀10Reacted by Andrew Straw, Kalan Snyder, Scott Robinson, brecht-derooms, Aaron Kutch, Alex, Corentin REGAL, damellp, Angad Tendulkar and musjj
3. tgrushka

   added a commit that references this issue on Jul 21, 2025

   feat: Add std::panic::Location support for error derive macro

   ...

   This issue will close once commit 36dc8b0 is merged into the 'main' branch.

   36dc8b0
4. vlad20012 commented on Nov 10, 2025

   

   vlad20012

   on Nov 10, 2025

   More actions

   A good explanation of why Location in errors is very useful: https://greptime.com/blogs/2024-05-07-error-rust#present-error-to-end-users

   There is an example of how an error report can looks with locations:

   Failed to handle protocol
   0: Failed to handle incoming content, query: blabla, at src/protocol/handler.rs:89:22
   1: Failed to reading next message at queue 5 of 10, at src/protocol/loop.rs:254:14
   2: Failed to decode `01010001001010001` to ProtocolHeader, at src/protocol/codec.rs:90:14
   3: serde_json(invalid character at position 1)