Why did cargo test test the documentation

Author: aceinetx

zenlang-cli/src/main.rs

@@ -3,7 +3,12 @@ use std::{
     fs::{self},
     io::Read,
 };
-use zenlang::{compiler, module, parser, stdlib, strong_u64::U64BitsControl, tokenizer, vm};
+use zenlang::{
+    compiler, module, parser, stdlib,
+    strong_u64::U64BitsControl,
+    tokenizer::{self, Tokenizer},
+    vm,
+};
 
 mod platform;
 

zenlang/src/ast/node.rs

@@ -11,7 +11,7 @@ pub trait Compile {
     /// Disable pushing for the current node
     ///
     /// This is needed in these cases, where with pushing would just flood the stack with unused data:
-    /// ```
+    /// ```ignore
     /// fn main {
     ///     123;
     /// }

zenlang/src/lib.rs

@@ -1,9 +1,9 @@
 //! ZenLang
 //!
 //! Primary programming language of ZenOS
-//! ```
+//! ```ignore
 //! fn main {
-//!     println("Hello from ZenLang");
+//!     println("Hello from ZenLang!");
 //!     return null;
 //! }
 //! ```

zenlang/src/tokenizer.rs

@@ -3,13 +3,7 @@
 //! Tokenizes ZenLang code into tokens
 //!
 //! ### Example
-//! ```
-//! fn main {}
-//! ```
-//! tokenizes into
-//! ```
-//! Fn, Identifier(main), Lbrace, Rbrace
-//! ```
+//! `fn main {}` -> `Fn, Identifier(main), Lbrace, Rbrace`
 use crate::unescape;
 use alloc::string::*;
 use libm::pow;