From d7738ec486fbc472e76529355f43eb8ee0e7e820 Mon Sep 17 00:00:00 2001 From: Daniel Verkamp Date: Tue, 28 May 2019 10:25:25 -0700 Subject: enumn: fix duplicate fn in doc tests Two parts of the documentation mention the generated `fn n`, which (as of Rust 1.35) causes a doc test failure. Change these code blocks to be ignored instead of executed to avoid the problem. BUG=None TEST=cargo test --doc -p enumn Change-Id: I9d08d2a35d65930bd2fa899256c00e1da643ba4f Signed-off-by: Daniel Verkamp Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/1632035 Reviewed-by: Zach Reizner Tested-by: kokoro --- enumn/src/lib.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'enumn/src/lib.rs') diff --git a/enumn/src/lib.rs b/enumn/src/lib.rs index 9f566e6..7a04303 100644 --- a/enumn/src/lib.rs +++ b/enumn/src/lib.rs @@ -51,7 +51,7 @@ //! attribute. If a `repr` is specified, the input to `n` will be required to be //! of that type. //! -//! ```rust +//! ```ignore //! use enumn::N; //! //! #[derive(N)] @@ -73,7 +73,7 @@ //! On the other hand if no `repr` is specified then we get a signature that is //! generic over a variety of possible types. //! -//! ```rust +//! ```ignore //! # enum E {} //! # //! impl E { -- cgit 1.4.1