Remove top-level re-exports

[taiki-e]

Closes #1854

[Nemo157]

What’s the feeling on removing all the doc(hidden) top-level reexports? It seems very odd to me to have undocumented exports for users to just accidentally stumble across.

[taiki-e]

What’s the feeling on removing all the doc(hidden) top-level reexports?

Personally I don't think I should depend on APIs that are not displayed in the documentation, so I would like to remove them, but unfortunately, some of the current documentation depends on these reexports.

It seems very odd to me to have undocumented exports for users to just accidentally stumble across.

I strongly agree.

[taiki-e]

So, I added a commit to reduce some top-level re-exports and changed the title of PR.

[taiki-e]

Seems intra-doc has been improved. All of top-level reexports can be removed.

[cramertj]

I personally use these pretty often and find having to import from two different modules just to get TryFutureExt and TryStreamExt pretty annoying. If no one else is bothered by this, I don't feel strongly enough to block, but I do think it's a decent-sized ergonomic hurdle.

[taiki-e]

@cramertj Okay, I separated the part not related to ext trait into #1858.

I personally use these pretty often and find having to import from two different modules just to get TryFutureExt and TryStreamExt pretty annoying. If no one else is bothered by this, I don't feel strongly enough to block, but I do think it's a decent-sized ergonomic hurdle.

Is this be resolved by merging try_{future, stream} modules into {future, stream} modules?

[cramertj]

That would help, but IMO use futures::{future::TryFutureExt, stream::TryStreamExt}; is still pretty noisy and the future and stream prefixes seem to stutter.

[taiki-e]

I noticed that the current one is useful when using with macro.

use futures::{select, join, FutureExt, TryFutureExt};

Also, the removal of reexports of items other than traits that I originally wanted to do is included in #1858.
So, I'm going to close this PR.