1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263
/*!
# The Problem
If you ever want to log when an error occurs and what caused it, you may find yourself using a `match` statement for every possible error instead of using the `?` operator.
This results in extremely verbose code. It's a pain to write and maintain.
# Introducing wrap-match!
wrap-match is an attribute macro that wraps your function in a `match` statement. Additionally, **it attaches rich error information to all statements using the `?` operator (aka try expressions).**
This allows you to know exactly what line and expression caused the error.
> **Note**
>
> wrap-match uses the `log` crate to log success and error messages. It does not expose the log crate for expanded functions to use; you must depend on it yourself.
>
> Additionally, **no messages will appear unless you use a logging implementation.** I recommend `env_logger`, but you can find a full list
> [here](https://docs.rs/log/#available-logging-implementations).
## Example
First, add this to your `Cargo.toml`:
```toml
[dependencies]
wrap-match = "1"
log = "*"
# You'll also want a logging implementation, for example `env_logger`
# More info here: https://docs.rs/log/#available-logging-implementations
```
Now you can use the `wrap_match` attribute macro:
```
# #[derive(Debug)] enum CustomError { Error }
#[wrap_match::wrap_match]
fn my_function() -> Result<(), CustomError> {
Err(CustomError::Error)?; // notice the ?; when the macro is expanded, it will be modified to include line number and expression
// If you need to return an error, just do `Err(CustomError::Error.into())`
Ok(())
}
```
This would expand to something like this (comments are not included normally):
```
# use wrap_match::__private::WrapMatchError; // don't use this! it's just to get it to compile
# #[derive(Debug)] enum CustomError { Error }
fn my_function() -> Result<(), CustomError> {
// This is where the original function is
fn _wrap_match_inner_my_function() -> Result<(), WrapMatchError<CustomError>> {
Err(CustomError::Error)
.map_err(|e| WrapMatchError {
// Here, line number and expression are added to the error
line_and_expr: Some((3, "Err(CustomError::Error)".to_owned())),
inner: e.into(), // This is so you can have `Box<dyn Error>` as your error type (however, we need to disable the `clippy::useless_conversion` lint for the entire function to allow this)
})?;
// If you need to return an error, just do `Err(CustomError::Error.into())`
Ok(())
}
match _wrap_match_inner_my_function() {
Ok(r) => {
::log::info!("Successfully ran my_function");
Ok(r)
}
Err(e) => {
if let Some((_line, _expr)) = e.line_and_expr {
::log::error!("An error occurred when running my_function (when running `{_expr}` on line {_line}): {:?}", e.inner);
} else {
::log::error!("An error occurred when running my_function: {:?}", e.inner);
}
Err(e.inner)
}
}
}
```
If we run this code, it would log this:
```log
[ERROR] An error occurred when running my_function (when running `Err(CustomError::Error)` on line 3): Error
```
As you can see, wrap-match makes error logging extremely easy while still logging information like what caused the error.
## Customization
wrap-match allows the user to customize success and error messages, as well as choosing whether or not to log anything on success.
### `success_message`
The message that's logged on success.
Available format specifiers:
- `{function}`: The original function name.
Default value: `Successfully ran {function}`
Example:
```
# #[derive(Debug)] enum CustomError { Error }
#[wrap_match::wrap_match(success_message = "{function} ran successfully!! 🎉🎉")]
fn my_function() -> Result<(), CustomError> {
Ok(())
}
```
This would log:
```log
[INFO] my_function ran successfully!! 🎉🎉
```
### `error_message`
The message that's logged on error, when line and expression info **is** available. Currently, this is only for try expressions (expressions with a `?` after them).
Available format specifiers:
- `{function}`: The original function name.
- `{line}`: The line the error occurred on.
- `{expr}`: The expression that caused the error.
- `{error}` or `{error:?}`: The error.
Default value: `` An error occurred when running {function} (caused by `{expr}` on line {line}): {error:?} ``
Example:
```
# #[derive(Debug)] enum CustomError { Error }
#[wrap_match::wrap_match(error_message = "oh no, {function} failed! `{expr}` on line {line} caused the error: {error:?}")]
fn my_function() -> Result<(), CustomError> {
Err(CustomError::Error)?;
Ok(())
}
```
This would log:
```log
[ERROR] oh no, my_function failed! `Err(CustomError::Error)` on line 3 caused the error: Error
```
### `error_message_without_info`
The message that's logged on error, when line and expression info **is not** available. This is usually triggered if you return an error yourself and use `.into()`.
Available format specifiers:
- `{function}`: The original function name.
- `{error}` or `{error:?}`: The error.
Default value: `An error occurred when running {function}: {error:?}`
Example:
```
# #[derive(Debug)] enum CustomError { Error }
#[wrap_match::wrap_match(error_message_without_info = "oh no, {function} failed with this error: {error:?}")]
fn my_function() -> Result<(), CustomError> {
Err(CustomError::Error.into())
}
```
This would log:
```log
[ERROR] oh no, my_function failed with this error: Error
```
### `log_success`
If `false`, nothing will be logged on success.
Default value: `true`
Example:
```
# #[derive(Debug)] enum CustomError { Error }
#[wrap_match::wrap_match(log_success = false)]
fn my_function() -> Result<(), CustomError> {
Ok(())
}
```
This would log nothing.
### `disregard_result`
If `true`, the resulting function will return `()` and throw away whatever the `Result` is. Useful for `main` functions.
Default value: `false`
Example:
```
# #[derive(Debug)] enum CustomError { Error }
#[wrap_match::wrap_match(disregard_result = true)]
fn main() -> Result<(), CustomError> {
Ok(())
}
```
The `main` function would be turned into this:
```
# use wrap_match::__private::WrapMatchError; // don't use this! it's just to get it to compile
# #[derive(Debug)] enum CustomError { Error }
fn main() {
fn _wrap_match_inner_main() -> Result<(), WrapMatchError<CustomError>> {
Ok(())
}
match _wrap_match_inner_main() {
# _ => {}
// the Result would be logged like normal, but it is not returned
}
}
```
## Limitations
wrap-match currently has the following limitations:
1. ~~wrap-match cannot be used on functions in implementations that take a `self` parameter. If you need support for this, please create a GitHub issue with your use case.~~ This is now supported!
However, it does require wrap-match to move the inner function out of the generated one, so it will add a new method to the implementation. This method is marked as deprecated, made private, and
is not shown in documentation. Hopefully this won't cause any issues.
1. wrap-match only supports `Result`s. If you need support for `Option`s, please create a GitHub issue with your use case.
1. `error_message` and `error_message_without_info` only support formatting `error` using the `Debug` or `Display` formatters. This is because of how we determine what formatting specifiers are used.
If you need support for other formatting specifiers (such as `:#?`), please create a GitHub issue with your use case.
1. wrap-match cannot be used on `const` functions. This is because the `log` crate cannot be used in `const` contexts.
If wrap-match doesn't work for something not on this list, please create a GitHub issue!
*/
#[doc(inline)]
pub use wrap_match_impl::wrap_match;
// Not public API.
#[doc(hidden)]
pub mod __private {
#[doc(hidden)]
pub struct WrapMatchError<E> {
pub line_and_expr: Option<(u32, String)>,
pub inner: E,
}
impl<E> From<E> for WrapMatchError<E> {
fn from(inner: E) -> Self {
Self {
line_and_expr: None,
inner,
}
}
}
}