I'd like to extract our pin macros into their own crate because they're useful for pinning in general and not tied to futures at all. Here's what I'd like to do:
- Remove the macros from the facade. Implementors can depend directly on the pin macro crate.
#[macro_use] is going away and an additional line in Cargo.toml ins't a burden. So the difference is really just use pin_utils::pin_mut; instead of use futures::pin_mut;
- Keep the source within the futures repository
- Possible names:
pin-utils (my favorite), pin-util, pin, pin-macros, pin-macro (one day we might want to include not-macro stuff in it as well, though)
- Independent versioning: Start with version 0.1.0
Thoughts?
@aturon
@cramertj
and anyone who's reading this π
I'd like to extract our pin macros into their own crate because they're useful for pinning in general and not tied to futures at all. Here's what I'd like to do:
#[macro_use]is going away and an additional line inCargo.tomlins't a burden. So the difference is really justuse pin_utils::pin_mut;instead ofuse futures::pin_mut;pin-utils(my favorite),pin-util,pin,pin-macros,pin-macro(one day we might want to include not-macro stuff in it as well, though)Thoughts?
@aturon
@cramertj
and anyone who's reading this π