Currently, we use the versions of pin_mut! and future::poll_fn from the futures crate. Now, core::pin::pin! and core::future::poll_fn are stable, so we can just use the stdlib versions of these APIs instead.
This allows us to reduce our dev dependencies on the futures crates down to just depending on futures_util in maitake-sync for select_biased!. Reducing the number of dev-deps will hopefully make compiling the tests a little faster. And, the stdlib version of pin! is way nicer than futures::pin_mut! as it can be on the right-hand side of an assignment, rather than requiring an assignment followed by a pin!.
Currently, we use the versions of
pin_mut!
andfuture::poll_fn
from thefutures
crate. Now,core::pin::pin!
andcore::future::poll_fn
are stable, so we can just use the stdlib versions of these APIs instead.This allows us to reduce our dev dependencies on the
futures
crates down to just depending onfutures_util
inmaitake-sync
forselect_biased!
. Reducing the number of dev-deps will hopefully make compiling the tests a little faster. And, the stdlib version ofpin!
is way nicer thanfutures::pin_mut!
as it can be on the right-hand side of an assignment, rather than requiring an assignment followed by apin!
.