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
//! This crate is intended to provide some convenience enums for mapping enums from one type to
//! another. This is intended as an expansion of `thiserror` that has more compile time mapping
//! between sets of enums as well as shortcutting `From` implementations.
//!
//! This is how to use wrapped the crate:
//!
//! ```rs
//! #![feature(more_qualified_paths)]
//!
//! treeerror::treeerror! {
//! #[derive(PartialEq, Debug)]
//! Root {
//! #[derive(PartialEq, Debug)]
//! Child0 {
//! #[derive(PartialEq, Debug)]
//! Child0_0 {
//! #[derive(PartialEq, Debug)]
//! Child0_0_0(&'static str),
//! },
//! #[derive(PartialEq, Debug)]
//! Child0_1 @unit,
//! Child0_2 @flatunit,
//! },
//! #[derive(PartialEq, Debug)]
//! Child1 {
//! #[derive(PartialEq, Debug)]
//! Child1_0 @unit,
//! #[derive(PartialEq, Debug)]
//! Child1_1 @unit,
//! Child1_2(u64),
//! Child1_3 @skipfrom (&'static str)
//! },
//! },
//! #[derive(PartialEq, Debug)]
//! SiblingRoot {
//! SiblingChild0(String),
//! SiblingChild1(&'static str)
//! }
//! }
//!
//! const MSG: &'static str = "hello from below";
//!
//! fn root_error() -> Result<(), Root> {
//! Err(MSG)?;
//!
//! unreachable!("error should have returned earlier");
//! }
//!
//! assert_eq!(
//! Err(Root::Child0(Child0::Child0_0(RenamedChild0_0::Child0_0_0(MSG)))),
//! root_error()
//! );
//! ```
//!
//! We also provide some utilities for generating simple `From` implementations.
//!
//! ```
//! #![feature(more_qualified_paths)]
//!
//! use treeerror::{from_many, from};
//!
//! #[derive(PartialEq, Debug)]
//! enum Root {
//! A(A),
//! }
//! #[derive(PartialEq, Debug)]
//! enum A {
//! Alpha(Alpha),
//! }
//! #[derive(PartialEq, Debug)]
//! enum Alpha {
//! One(One),
//! }
//! #[derive(PartialEq, Debug)]
//! enum One {
//! Child(Child),
//! }
//! #[derive(PartialEq, Debug)]
//! struct Child;
//!
//! from_many!(Root: A, A, Alpha, One, Child);
//! from_many!(A: Alpha, Alpha, One, Child);
//! from_many!(Alpha: One, One, Child);
//! from!(One = Child(Child));
//!
//! const MSG: &'static str = "hello from below";
//!
//! fn root_error() -> Result<(), Root> {
//! Err(Child)?;
//!
//! unreachable!("error should have returned earlier");
//! }
//!
//! assert_eq!(
//! Err(Root::A(A::Alpha(Alpha::One(One::Child(Child))))),
//! root_error()
//! );
//! ```
//!
//! You'll notice that there are many `from_many` call here -- automatically generating this
//! tree is not yet complete and in progress.
//!
//! We can also handle "flatter" error structures where, instead of nesting these enums by
//! wrapping them, we destructure the internal values instead.
//!
//! There are several ways to use this as well, but here's the most basic use case.
//!
//! ```
//! #![feature(more_qualified_paths)]
//!
//! use treeerror::map_enum;
//!
//! #[derive(PartialEq, Eq, Debug)]
//! pub enum ParentError {
//! Child(&'static str),
//! }
//!
//! #[derive(PartialEq, Eq, Debug)]
//! pub enum ChildError {
//! SomeError(&'static str),
//! }
//!
//! map_enum!(ChildError > ParentError {
//! SomeError > Child
//! });
//!
//! const MSG: &'static str = "hello there";
//!
//! fn parent_error() -> Result<(), ParentError> {
//! Err(ChildError::SomeError(MSG))?;
//!
//! unreachable!("error should have returned earlier");
//! }
//!
//! assert_eq!(
//! Err(ParentError::Child(MSG)),
//! parent_error(),
//! );
//! ```
//!
//! Some things that remain: combining all of this in a nice interface to autogenerate the
//! error chains, as well as packaging all of this stuff in a way to enable better error
//! messages during compilation. This potentially includes a proc macro rewrite to enable
//! better error messages and configurability.