Hide the event_count module.

By placing the code for the parse executable inside a module inside the organic library, we only need to expose the entrypoint publicly rather than all functions it calls. This hides the event_count module, but I will be expanding the practice to the rest of the code base shortly. This is important for not inadvertently promising stability w.r.t. semver for essentially internal functions for development tools.

It was the parse binary, not compare.

src/lib.rs

@@ -4,6 +4,7 @@
 #![feature(is_sorted)]
 #![feature(test)]
 #![feature(iter_intersperse)]
+#![feature(exact_size_is_empty)]
 // TODO: #![warn(missing_docs)]
 #![allow(clippy::bool_assert_comparison)] // Sometimes you want the long form because its easier to see at a glance.
 
@@ -11,6 +12,7 @@ extern crate test;
 
 #[cfg(feature = "compare")]
 pub mod compare;
+pub mod parse_cli;
 #[cfg(any(feature = "compare", feature = "wasm", feature = "wasm_test"))]
 pub mod util;
 #[cfg(any(feature = "wasm", feature = "wasm_test"))]
@@ -21,7 +23,7 @@ pub mod wasm_test;
 mod context;
 mod error;
 #[cfg(feature = "event_count")]
-pub mod event_count;
+mod event_count;
 mod iter;
 pub mod parser;
 pub mod types;