Ignore clippy new_ret_no_self warnings

Author: cramertj

futures-channel/src/mpsc/queue.rs

@@ -80,6 +80,7 @@ unsafe impl<T: Send> Send for Queue<T> { }
 unsafe impl<T: Send> Sync for Queue<T> { }
 
 impl<T> Node<T> {
+    #[allow(clippy::new_ret_no_self)]
     unsafe fn new(v: Option<T>) -> *mut Node<T> {
         Box::into_raw(Box::new(Node {
             next: AtomicPtr::new(ptr::null_mut()),

futures-executor/src/thread_pool.rs

@@ -72,6 +72,7 @@ impl ThreadPool {
     /// See documentation for the methods in
     /// [`ThreadPoolBuilder`](ThreadPoolBuilder) for details on the default
     /// configuration.
+    #[allow(clippy::new_ret_no_self)]
     pub fn new() -> Result<ThreadPool, io::Error> {
         ThreadPoolBuilder::new().create()
     }

futures-util/src/lock.rs

@@ -60,6 +60,7 @@ impl<T> BiLock<T> {
     /// will only be available through `Pin<&mut T>` (not `&mut T`) unless `T` is `Unpin`.
     /// Similarly, reuniting the lock and extracting the inner value is only
     /// possible when `T` is `Unpin`.
+    #[allow(clippy::new_ret_no_self)]
     pub fn new(t: T) -> (BiLock<T>, BiLock<T>) {
         let arc = Arc::new(Inner {
             state: AtomicUsize::new(0),