@@ -56,7 +56,7 @@ macro_rules! throw_validation_failure {
5656/// This lets you use the patterns as a kind of validation list, asserting which errors
5757/// can possibly happen:
5858///
59- /// ```
59+ /// ```ignore(illustrative)
6060/// let v = try_validation!(some_fn(), some_path, {
6161/// Foo | Bar | Baz => { "some failure" },
6262/// });
@@ -65,7 +65,7 @@ macro_rules! throw_validation_failure {
6565/// The patterns must be of type `UndefinedBehaviorInfo`.
6666/// An additional expected parameter can also be added to the failure message:
6767///
68- /// ```
68+ /// ```ignore(illustrative)
6969/// let v = try_validation!(some_fn(), some_path, {
7070/// Foo | Bar | Baz => { "some failure" } expected { "something that wasn't a failure" },
7171/// });
@@ -74,7 +74,7 @@ macro_rules! throw_validation_failure {
7474/// An additional nicety is that both parameters actually take format args, so you can just write
7575/// the format string in directly:
7676///
77- /// ```
77+ /// ```ignore(illustrative)
7878/// let v = try_validation!(some_fn(), some_path, {
7979/// Foo | Bar | Baz => { "{:?}", some_failure } expected { "{}", expected_value },
8080/// });
0 commit comments