@@ -30,9 +30,9 @@ impl Report {
30
30
31
31
/// Create a new error object from a printable error message.
32
32
///
33
- /// If the argument implements std::error::Error, prefer `Report::new`
33
+ /// If the argument implements [` std::error::Error`] , prefer `Report::new`
34
34
/// instead which preserves the underlying error's cause chain and
35
- /// backtrace. If the argument may or may not implement std::error::Error
35
+ /// backtrace. If the argument may or may not implement [` std::error::Error`]
36
36
/// now or in the future, use `miette!(err)` which handles either way
37
37
/// correctly.
38
38
///
@@ -206,7 +206,7 @@ impl Report {
206
206
/// Create a new error from an error message to wrap the existing error.
207
207
///
208
208
/// For attaching a higher level error message to a `Result` as it is
209
- /// propagated, the [crate::WrapErr] extension trait may be more
209
+ /// propagated, the [`WrapErr`]( crate::WrapErr) extension trait may be more
210
210
/// convenient than this function.
211
211
///
212
212
/// The primary reason to use `error.wrap_err(...)` instead of
@@ -233,7 +233,7 @@ impl Report {
233
233
unsafe { Report :: construct ( error, vtable, handler) }
234
234
}
235
235
236
- /// Compatibility re-export of wrap_err for interop with `anyhow`
236
+ /// Compatibility re-export of ` wrap_err` for interop with `anyhow`
237
237
pub fn context < D > ( self , msg : D ) -> Self
238
238
where
239
239
D : Display + Send + Sync + ' static ,
0 commit comments