Hide fairrwlock module in tests.

Author: tnull

lightning/src/util/fairrwlock.rs

@@ -1,4 +1,4 @@
-use std::sync::{TryLockResult, LockResult, RwLock, RwLockReadGuard, RwLockWriteGuard};
+use std::sync::{LockResult, RwLock, RwLockReadGuard, RwLockWriteGuard};
 use std::sync::atomic::{AtomicUsize, Ordering};
 
 /// Rust libstd's RwLock does not provide any fairness guarantees (and, in fact, when used on
@@ -17,7 +17,6 @@ pub struct FairRwLock<T> {
 	waiting_writers: AtomicUsize,
 }
 
-#[cfg_attr(test, allow(dead_code))]
 impl<T> FairRwLock<T> {
 	pub fn new(t: T) -> Self {
 		Self { lock: RwLock::new(t), waiting_writers: AtomicUsize::new(0) }
@@ -33,11 +32,6 @@ impl<T> FairRwLock<T> {
 		res
 	}
 
-	#[allow(dead_code)]
-	pub fn try_write(&self) -> TryLockResult<RwLockWriteGuard<T>> {
-		self.lock.try_write()
-	}
-
 	pub fn read(&self) -> LockResult<RwLockReadGuard<T>> {
 		if self.waiting_writers.load(Ordering::Relaxed) != 0 {
 			let _write_queue_lock = self.lock.write();

lightning/src/util/mod.rs

@@ -25,6 +25,7 @@ pub mod persist;
 pub(crate) mod atomic_counter;
 pub(crate) mod byte_utils;
 pub(crate) mod chacha20;
+#[cfg(not(test))]
 #[cfg(feature = "std")]
 pub(crate) mod fairrwlock;
 #[cfg(fuzzing)]