Expose thread_manager for debugging purposes

5 years ago · 2dc3cb40b6
parent 0408a5aea0
commit 2dc3cb40b6
2 changed files with 3 additions and 3 deletions
--- a/Cargo.toml
+++ b/Cargo.toml
@ -1,6 +1,6 @@
 [package]
 name = "bdflib"
-version = "0.3.5"
+version = "0.3.6"
 authors = ["trivernis <trivernis@gmail.com>"]
 edition = "2018"
 license-file = "LICENSE"
--- a/src/io.rs
+++ b/src/io.rs
@ -12,7 +12,7 @@ use crossbeam_utils::sync::WaitGroup;
 const ENTRIES_PER_CHUNK: u32 = 100_000;

 #[derive(Debug)]
-struct ThreadManager<T1, T2> {
+pub struct ThreadManager<T1, T2> {
    pub sender_work: Sender<T1>,
    pub receiver_work: Receiver<T1>,
    pub sender_result: Sender<T2>,
@ -38,7 +38,7 @@ pub struct BDFWriter {
    head_written: bool,
    compressed: bool,
    compression_level: u32,
-    thread_manager: ThreadManager<GenericChunk, Vec<u8>>,
+    pub thread_manager: ThreadManager<GenericChunk, Vec<u8>>,
 }

 impl<T1, T2> ThreadManager<T1, T2> {