@@ -56,7 +56,7 @@ macro_rules! throw_validation_failure {
56
56
/// This lets you use the patterns as a kind of validation list, asserting which errors
57
57
/// can possibly happen:
58
58
///
59
- /// ```
59
+ /// ```ignore(illustrative)
60
60
/// let v = try_validation!(some_fn(), some_path, {
61
61
/// Foo | Bar | Baz => { "some failure" },
62
62
/// });
@@ -65,7 +65,7 @@ macro_rules! throw_validation_failure {
65
65
/// The patterns must be of type `UndefinedBehaviorInfo`.
66
66
/// An additional expected parameter can also be added to the failure message:
67
67
///
68
- /// ```
68
+ /// ```ignore(illustrative)
69
69
/// let v = try_validation!(some_fn(), some_path, {
70
70
/// Foo | Bar | Baz => { "some failure" } expected { "something that wasn't a failure" },
71
71
/// });
@@ -74,7 +74,7 @@ macro_rules! throw_validation_failure {
74
74
/// An additional nicety is that both parameters actually take format args, so you can just write
75
75
/// the format string in directly:
76
76
///
77
- /// ```
77
+ /// ```ignore(illustrative)
78
78
/// let v = try_validation!(some_fn(), some_path, {
79
79
/// Foo | Bar | Baz => { "{:?}", some_failure } expected { "{}", expected_value },
80
80
/// });
0 commit comments