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
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
//! # Skerry: Super Kool ERRors Yoh
//!
//! Example:
//! ```rust
//! use skerry::*;
//!
//! // 1. Define your error boundary
//! # struct ErrorFromLib;
//! #[skerry_mod]
//! pub mod errors {
//! pub struct DatabaseErr;
//! pub struct AuthErr;
//! pub struct ValidationErr;
//!
//! pub struct LibErr(ErrorFromLib);
//! impl From<ErrorFromLib> for LibErr {
//! fn from(val: ErrorFromLib) -> Self {
//! Self(val)
//! }
//! }
//! }
//!
//! // 2. Generate a 'low_level' error enum automatically
//! #[skerry_fn]
//! fn check_auth() -> Result<(), AuthErr> {
//! Err(CheckAuthError::AuthErr(AuthErr))
//! }
//!
//! # fn lib_fn_that_returns_error() -> Result<(), ErrorFromLib> {
//! # Err(ErrorFromLib)
//! # }
//!
//! // 3. Use '&' to expand and bubble up sub-errors seamlessly
//! #[skerry_fn]
//! pub fn Controller() -> Result<(), (ValidationErr, LibErr, &CheckAuthError)> {
//! // ValidationErr is local, AuthErr is pulled in from check_auth via '&'
//! check_auth()?;
//!
//! // You can also automatically bubble up library errors as long as an error from
//! // `#[skerry_mod]` implements `From` for it
//! lib_fn_that_returns_error()?;
//!
//! Ok(())
//! }
//! ```
//!
//! Skerry is a type-safe error management framework designed to kill boilerplate.
//! It allows you to define a global error set while returning granular, function-specific
//! enums that are automatically generated at compile-time.
//!
//! ## Core Workflow
//!
//! 1. Define all possible error structs in a `#[skerry_mod]`.
//! 2. Mark functions with `#[skerry_fn]`.
//! 3. Use the `&` operator to bubble up errors from sub-functions without manually mapping variants.
//!
//! ---
//!
//! ## The Error Module
//! Every project needs one module (usually `errors.rs`) that acts as the source of truth.
//!
//! ```rust
//! pub use skerry::*; // Recommended to be pub for easier macro expansions
//!
//! #[skerry_mod]
//! mod errors {
//! pub struct ErrA;
//! pub struct ErrB;
//! pub struct ErrC;
//! pub struct DatabaseErr;
//! }
//! ```
//! *Note: When using errors in any other file, import them via `crate::errors::*;` instead
//! of individual imports to ensure the macros can resolve the paths correctly.*
//!
//! ---
//!
//! ## Function-Specific Enums
//!
//! By using `#[skerry_fn]`, you define a return type using a tuple of error structs.
//! Skerry transforms this into a unique enum named `{FunctionName}Error`.
//!
//! ```rust
//! # pub use skerry::*;
//! # #[skerry_mod]
//! # mod errors {
//! # pub struct ErrA;
//! # pub struct ErrB;
//! # pub struct ErrC;
//! # pub struct DatabaseErr;
//! # }
//! #[skerry_fn]
//! pub fn low_level() -> Result<(), (ErrA, ErrB)> {
//! // Generates LowLevelError { ErrA(ErrA), ErrB(ErrB) }
//! Err(LowLevelError::ErrA(ErrA)) // You can also type Err(ErrA.into())
//! }
//! ```
//!
//! ---
//!
//! ## The Ampersand (`&`) Expansion
//!
//! The `&` operator is the heart of Skerry. When you put `&OtherFnError` in your return tuple:
//!
//! * **Expansion**: It pulls all variants from `OtherFnError` into your current function's list.
//! * **Promotion**: It allows the `?` operator to work seamlessly for that function's return type.
//! * **Deduplication**: Variants are deduplicated automatically. If `ErrA` is added manually
//! and also exists inside a `&` expansion, only one variant is generated.
//!
//! ```rust
//! # pub use skerry::*;
//! # #[skerry_mod]
//! # mod errors {
//! # pub struct ErrA;
//! # pub struct ErrB;
//! # pub struct ErrC;
//! # pub struct DatabaseErr;
//! # }
//! # #[skerry_fn]
//! # pub fn low_level() -> Result<(), (ErrA, ErrB)> {
//! # // Generates LowLevelError { ErrA(ErrA), ErrB(ErrB) }
//! # Err(LowLevelError::ErrA(ErrA)) // You can also type Err(ErrA.into())
//! # }
//! #[skerry_fn]
//! pub fn high_level() -> Result<(), (ErrC, &LowLevelError)> {
//! // 1. Sees ErrC -> Adds variant
//! // 2. Sees &LowLevelError -> Inspects LowLevelError, finds (ErrA, ErrB)
//! // 3. Final HighLevelError contains variants: ErrA, ErrB, ErrC
//!
//! low_level()?; // Bubbles up automatically
//! Ok(())
//! }
//! ```
//!
//! The syntax below has the exact same effects, `&LowLevelError` is nothing more than syntatic sugar
//!
//! ```rust
//! # pub use skerry::*;
//! # #[skerry_mod]
//! # mod errors {
//! # pub struct ErrA;
//! # pub struct ErrB;
//! # pub struct ErrC;
//! # pub struct DatabaseErr;
//! # }
//! # #[skerry_fn]
//! # pub fn low_level() -> Result<(), (ErrA, ErrB)> {
//! # // Generates LowLevelError { ErrA(ErrA), ErrB(ErrB) }
//! # Err(LowLevelError::ErrA(ErrA)) // You can also type Err(ErrA.into())
//! # }
//! #[skerry_fn]
//! pub fn high_level() -> Result<(), (ErrA, ErrB, ErrC)> {
//! // ...
//! # Ok(())
//! }
//! ```
//!
//! In the cases above the generated enum looks like this
//! ```rust
//! # struct ErrA;
//! # struct ErrB;
//! # struct ErrC;
//! pub enum HighLevelError {
//! ErrA(ErrA),
//! ErrB(ErrB),
//! ErrC(ErrC),
//! }
//! ```
//! ## Using Skerry inside Impl Blocks
//!
//! Skerry provides the `#[skerry_impl]` attribute to handle methods within `impl` blocks.
//! This attribute coordinates with `#[skerry_fn]` to split the generated code:
//!
//! 1. **Top-Level**: The error enums are generated outside the `impl` block.
//! 2. **Method-Level**: The method signature is updated, and all `?` operators are
//! automatically transformed to wrap errors into `GlobalErrors`.
//!
//! ### Example
//!
//! ```rust
//! use skerry::*;
//!
//! # #[skerry_mod]
//! # mod errors {
//! # pub struct ConnectionFailed;
//! # }
//! # #[skerry_fn]
//! # pub fn remote_call() -> Result<(), (ConnectionFailed)> {
//! # Ok(())
//! # }
//! #
//! pub struct Database;
//!
//! #[skerry_impl(prefix(Database))] // Optional prefix for functions inside impl block
//! impl Database {
//! #[skerry_fn]
//! pub fn connect(&self) -> Result<(), (&RemoteCallError)> {
//! remote_call()?;
//! Ok(())
//! }
//! }
//!
//! fn main() {
//! let db = Database;
//! let result: Result<(), DatabaseConnectError> = db.connect();
//! assert!(result.is_ok());
//! }
//! ```
//!
//! ---
//!
//! ## Compile-Time Safety
//!
//! Skerry uses a custom trait system (`MissingConvert`) to verify error bounds at
//! compile-time. If you try to use `?` on a function whose errors are not represented
//! in your current return tuple, the compiler will refuse to build.
pub use ;