Fix conflicting async io feature compilation

Previously, enabling `with-tokio` would also activate the `default` feature
(`with-futures`), because Cargo includes default features by design.
This would lead to a compilation error due to duplicate definitions from both
`use` statements.

This commit replaces the separate `#[cfg]` blocks with a single `cfg_if`
macro. This creates a prioritized selection for the io backend.

Author: filipeom

Cargo.toml

@@ -12,6 +12,7 @@ documentation = "https://docs.rs/memcache-async"
 homepage = "https://github.com/vavrusa/memcache-async"
 
 [dependencies]
+cfg-if = "1.0.1"
 futures = { version = "0.3" }
 tokio = { version = "1.37", features = ["io-util"] }
 

src/ascii.rs

@@ -1,11 +1,22 @@
 //! This is a simplified implementation of [rust-memcache](https://github.com/aisk/rust-memcache)
 //! ported for AsyncRead + AsyncWrite.
 use core::fmt::Display;
-#[cfg(feature = "with-futures")]
-use futures::io::{AsyncBufReadExt, AsyncRead, AsyncReadExt, AsyncWrite, AsyncWriteExt, BufReader};
 
-#[cfg(feature = "with-tokio")]
-use tokio::io::{AsyncBufReadExt, AsyncRead, AsyncReadExt, AsyncWrite, AsyncWriteExt, BufReader};
+use cfg_if::cfg_if;
+
+cfg_if! {
+    // The order here matters. If both features are enabled,
+    // this one will be chosen, avoiding a conflict.
+    if #[cfg(feature = "with-tokio")] {
+        use tokio::io as async_io;
+    } else if #[cfg(feature = "with-futures")] {
+        use futures::io as async_io;
+    } else {
+        compile_error!("An async I/O feature ('with-tokio' or 'with-futures') must be enabled.");
+    }
+}
+
+use async_io::{AsyncBufReadExt, AsyncRead, AsyncReadExt, AsyncWrite, AsyncWriteExt, BufReader};
 
 use std::collections::HashMap;
 use std::io::{Error, ErrorKind};