Taiki Endo

@seanmonstar > The only thing I'm unsure about is having `trait Stream` defined _inside_ `futures-core` as v1.0, when it may soon be added to the standard library. It's possible for...

> Having a local `Stream` and making a future version start re-exporting it from `std` would be a breaking change (even if there is a patch release doing the re-exporting...

Another concern with using build-scripts is their compatibility with non-cargo build systems that do not run build-scripts. In this case, the trait imported from futures and the trait imported from...

cfg-accessible isn't stable yet, and [a stable alternative](https://docs.rs/autocfg/1.0.1/autocfg/struct.AutoCfg.html#method.probe_path) requires build-script, so I've written the above example using build-script. Once cfg-accessible is stable, we can do it without build-script, as you...

FYI: I've created a demo of how `Stream` re-export trick implemented: https://github.com/taiki-e/futures-compat-experiment

https://github.com/rust-lang/futures-rs/pull/2335

> I also have concerns around the naming of `poll!`: [rust-lang/rust#81050 (comment)](https://github.com/rust-lang/rust/pull/81050#issuecomment-771279864) @tmandry I understand your concerns, but basically, I don't think we really need to rename it. `future::ready` is...

> I think we're a _long_ way off having async-block defined IO types. @Nemo157 Interesting. Do you think it's the timing when type_alias_impl_trait is stable? Or will it take longer?

@yoshuawuyts I think #1989 and #1894 written by @Matthias247 have some great explanations. The main issue is it needs to specify the trait requirement at the bounds level like `select`....

thanks. first, we need to link to module instead of trait, in top page. (like io, channel, executor, etc.). next, we need to improve module docs.